I am trying to deploy and test a Universal Windows App to a Surface Pro 3 directly from Visual Studio 2013 (Update 4) and I am unable to launch the App (by hitting F5). I am running into the following error and not able to find a fix to it. There are a bunch of solutions of DEP0700 errors online, but none of them work for the specific sub-error message Cannot map the serial well-known device name to a device interface GUID (blah blah blah)
Here is the error that I am seeing
Error : DEP0700 : Registration of the app failed. c:\Builds\TestAppRT\AppX\AppxManifest.xml(38,6): error 0x80070002:
Cannot map the serial well-known device name to a device interface GUID for the 11156705-8b60-4c7f-a75f-f8c7516401fc_1.0.0.0_neutral__1g7p71hbj7m7y package.
Check that the device name is correct. (0x80073cf6)
Have you declared any serial communication in your AppxManifest file?
If your other apps work, your issue might be because opening/editing ApxManifest file in the designer. Try making a new solution, and edit the manifest through only through XML Editor, if required & do not open with the designer.
Reference for more information:
http://ms-iot.github.io/content/en-US/win10/samples/SerialSample.htm
"Visual Studio 2015 has a known bug in the Manifest Designer (the visual editor for appxmanifest files) that affects the serialcommunication capability. If
your appxmanifest adds the serialcommunication capability, modifying your appxmanifest with the designer will corrupt your appxmanifest (the Device xml child will be lost). You can workaround this problem by hand editting the appxmanifest by right-clicking your appxmanifest and selecting View Code from the context menu."
Related
I'm using Application Insights in my application. The App runs without any warnings or problems but when I packaged the App and ran a Windows App Certification Kit on it, it failed stating this:
FAILED General metadata correctness test
•Error Found: The general metadata correctness test detected the
following errors:◦The type
Microsoft.ApplicationInsights.Extensibility.TelemetryConfiguration
referenced by type
Microsoft.ApplicationInsights.Extensibility.RuntimeTelemetry.RemoteDependencyModule
in file
Microsoft.ApplicationInsights.Extensibility.RuntimeTelemetry.winmd was
not found. All types referenced in metadata files must be
discoverable. ◦The type
Microsoft.ApplicationInsights.Extensibility.ISupportConfiguration
referenced by type
Microsoft.ApplicationInsights.Extensibility.RuntimeTelemetry.RemoteDependencyModule
in file
Microsoft.ApplicationInsights.Extensibility.RuntimeTelemetry.winmd was
not found. All types referenced in metadata files must be
discoverable.
Does anyone have any idea how to resolve this?
It looks like you use very old Application Insights SDK version. I guess but probably it is 0.14 (The one that you get from VS 2013, this version is not updating any more because packages were renamed). You should remove that SDK version and try the new one: https://www.nuget.org/packages/Microsoft.ApplicationInsights.WindowsApps/
RuntimeTelemetry.winmd is not there any more.
I am trying to access the WinRT sensors from a Win32 desktop application using C++/CX as mentioned here: https://software.intel.com/en-us/articles/using-winrt-apis-from-desktop-applications
When I include the C++/CX header file it causes an error when building the Win32 project.
Exact error text: "error C1190: managed targeted code requires a '/clr' option."
Since I am not using /clr code at all, this is a confusing error.
Any suggestions? Please educate me if there is a better way to do this.
The error you are getting is because you are compiling some files without /ZW option for compiler. Since you are able compile at least some files with WinRT extensions, but not others, your project configuration is inconsistent.
The option /ZW (enable WinRT extensions) has to be configured on the level of project (and not on the level of individual files). There are two ways to ensure your settings are consistent. First method is through UI in Visual Studio -- you have to go through all platforms/configurations on the project and ensure /ZW is enabled, then got through all indivudual .cpp files, and ensure they don't override project level settings. This is tedious and error prone. The easier method is to open .vcxproj in notepad and do the following:
Add this section at the beginnig of the file, under root Project node:
<ItemDefinitionGroup>
<ClCompile>
<CompileAsWinRT>true</CompileAsWinRT>
</ClCompile>
</ItemDefinitionGroup>
Search and remove any other places where <CompileAsWinRT> is defined.
I have a data driven subscription that renders the report in PDF. SSRS 2012, Win 2008 R2 (on Hyper-V) is used.
I have looked in ExecutionLog3, the shared data sets all successfully refresh, the reports successfully render and are output to the correct folder.
I did read somewhere that when rendering the reports in IE that the user needed permissions to the Temporary Internet Files folder, however I don't know if this is valid for data driven subscriptions? I did add the execution account (a local user) to have read/write permissions on the ReportServer temp internet folder.
Apart from this I have no idea what to look for to troubleshoot this issue? Any suggestions will be welcomed.
EDIT - 2012-11-19
Have found the following unhandled exception error in the ReportServer log:
ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.RenderingObjectModelException: , Microsoft.ReportingServices.ReportProcessing.RenderingObjectModelException: A generic error occurred in GDI+. ---> System.Runtime.InteropServices.ExternalException: A generic error occurred in GDI+.
at System.Drawing.Image.Save(Stream stream, ImageCodecInfo encoder, EncoderParameters encoderParams)
at Microsoft.Reporting.Chart.WebForms.Chart.Save(Stream imageStream, ChartImageFormat format)
at Microsoft.ReportingServices.OnDemandReportRendering.ChartMapper.GetImage(ImageType imageType)
--- End of inner exception stack trace ---;
It turns out that the GDI+ drivers needed updating on Windows 2008 R2 Server and is a known issue. If you want to know what version of GDI+ you have then do a file search for gdiplus.dll.
I posted the same question here and got a response saying to update the drivers via a hotfix, which can be found at this link, and it provides the version of the gdiplus.dll that will be installed with the hotfix, so you can compare if there is a version change necessary.
You need to request the hotfix, and an email will be sent to you giving you the download location.
This also solved the issue of images not rendering as well as charts
I created a Windows Phone 8 project from Microsofts XAML - Direct3d template in Visual Studio 2012.
When I place a breakpoint in the C#-Xaml project and start debugging, the debugger stops on the breakpoint with no problem.
However, if I place a breakpoint in the C++-Direct3D component project, the breakpoint never gets hit and the debugger complains that there are no symbols loaded and the module browser says the Binary was not built with debug information.
I have triple checked the project settings for the C++ component, and debug symbols are indeed being built.
How can I get debugging and breakpoints in the C++ component working?
From the Module window in VS 2012:
PhoneDirect3DXamlAppComponent.winmd C:\Data\Programs\{0827E110-DAB9-49BB-A331-0A7FF54F418C}\Install\PhoneDirect3DXamlAppComponent.winmd No N/A Binary was not built with debug information. 10 11/9/2012 12:29 PM 03640000-03642000 [2568] TaskHost.exe [1] Silverlight AppDomain
I'm not sure this is the fix for your problem, but anyway you should switch the debugger from "Managed Only" to "Native Only". You can do that in the properties screen of your managed project. (probably under "UI Task")
Error 1 Manifest references file 'Bing.Maps.dll' which is not part of the payload. C:\Users\xxx\Desktop\xxx\Applicationxx\Applicationxx\Package.appxmanifest Application7
I added this into a existing Metro application and its giving me that error, anyone has solution to it?
Go to the properties of the project and under Build, you will see Platform Target. Choose either x64 or x86 instead of Any CPU and it should be solved.
~Guo Hong
To correctly reference Bing Maps for a Metro app...
Go to: Project -> Add Reference -> Windows -> Extensions
Now, select both the "Bing Maps for ..." and also "Microsoft Visual C++ Runtime Package"
If you don't select the 2nd package, things will seem to be fine until you try to actually deploy your app.