When I run my program in debug mode, it runs nicely. Now that I want to upload it to the Windows Phone Store, it creates the App Package, but when running the Windows App Certification Kit, it returns the following error:
General metadata correctness test - failed
with the reason:
In the Winmd-File "myBackgroundPart.winmd" (that's my RunTime Component) there is missing "WindowsRuntime 1.3" or "WindowsRuntime 1.2" in the versionstring. The versionstring of the file is "WindowsRuntime 1.4;CLR v4.0.30319".
My environment is Visual Studio 2015 CTP5. The error message suggests, that my WinRT is too new for Store!? How do I downgrade it then?
Edit
This was an issue with VS2015 CTP5, with the new released CTP6 yesterday it was solved.
You need to build your app using Visual Studio 2013 (Update 4 is the latest). Note that Visual Studio 2015 does not have a "go live" license, meaning you can't use it for production purposes anyway. You need to wait until it is released.
Also, when you built the component, what Project Type did you choose? If you built a project for Windows 8.x then I don't think it should have used version 1.4 metadata. Did you build / test on Windows 10 Preview by any chance?
Related
I have TeamCity 2019.1.5 with most recent Visual Studio Tool 2017 installed:
I have a project which uses C# 7.1 features, and it compiles locally just fine in VS 2017, and I made sure it has <LangVersion>latest</LangVersion> in CSPROJ file. But when I run it from TeamCity (agent is on the same server) with the following build step:
it fails with the following error in the logs:
[Csc] Services\MappingService.cs(1942, 40): error CS8107: Feature 'default literal' is not available in C# 7.0. Please use language version 7.1 or greater.
If I start VS2017 command prompt on the server and go to the project's folder and run msbuild tt.csproj /target:Rebuild it works fine: compiles and I do not get any errors. Needless to say, if I remove C# 7.1-specific code, everything works in the current configuration.
I installed Visual Studio Tool 2019 and with MSBuild 16 it works without any problems as well. But I prefer to use 2017 tools so both server and dev environments are the same. What can cause this issue?
I had this problem and fixed it by fixing the solution configuration in the build step configuration. It needs to be set to either "Debug" or "Release". Mine was set to a parameter, which resolved to something other than one of those values.
I have previously given up on installing OpenCV on my Windows 7 PC but now it has come back to haunt me, this time I'm trying to build its libraries using Visual Studio Community 2015.
I have tried finding a decent procedure on how to install it but they all sound simple until you encounter tons of errors when building ALL_BUILD in VS.
Here's what I did:
Downloaded the OpenCV 3.1 installer
Ran the installer and installed OpenCV in C:\
Added the OPENCV_DIR environment variable pointing to C:\opencv\build
Opened cmake-gui and set the source and build folders to C:\opencv\sources and C:\opencv\build, respectively
Clicked Configure, unchecked WITH_VTK option, clicked Configure again, then clicked Generate
Opened the generated solution file in C:\opencv\build
Right-clicked on the ALL_BUILD project and clicked Build
Only 11 projects were successfully built and 79 failed. The procedure they have on the OpenCV website is so outdated that it made me give up a long time ago. And there are several other resources that give equally confusing instructions.
Your help will be appreciated!
Upon further investigation, I saw this error frequently generated through build:
nvcc fatal : nvcc cannot find a supported version of Microsoft Visual Studio. Only the versions 2010, 2012, and 2013 are supported
This is caused by CUDA not supporting Visual Studio 2015 yet. So, I unchecked WITH_CUDA in cmake-gui, clicked Generate, opened the generated OpenCV solution file and built ALL_BUILD. No errors were generated after that.
I have a VS 2013 solution with a WP8 App, a WP8 Library for my viewmodels, a WP8 Unit Test project to test my library and other standard unit tests projects. The solution is under TFS 2012 source control, the build controller is setup and it correctly build my solution.
But my WP8 specific tests are not ran after automatic build. All other standard Unit Tests projects run well.
Some additional infos:
the ".xap" package for the test project is well generated
the build process Template (Default Template) is setup to use "Visual Studio Test Runner"
the build agent is running interactively
when i launch vstest.console.exe from the command line, giving the ".xap" package as argument, the test are well discovered and executed
I'am i missing something in the configuration ?
Windows Phone apps are currently not supported on Team Build, as documented here.
Feature | Windows Phone | Windows Store App
Team Build support | Not supported. | Includes support for running unit tests as part of Team Build.
There are a few unsupported work-arounds to solve your issue, more an be found here.
I just wanted to start building apps for Windows Phone but after creating a new project for Windows Phone and hitting the F5 button to run it, I get these errors:
1>MakePri : error 0x80073b0a: Initializing Indexer
1>MakePRI : error 0xdef00042: Invalid qualifier: Scale
Note this is a new project. I haven't modified anything in it. I also tried other templates and none of them ran successfully. The verbose build log was quite large but if you want to, I can post it here. I checked and the the installation of the Visual Studio is full (SDK and everything else is installed.)
I'm using Visual Studio 2013 Update 2 and so far I haven't had any problem with it. The project is targeting Windows Phone 8.1
I receive the following error on the Windows App Certification Kit for Windows 8.1.
The app manifest test detected the following errors:XXX takes a
dependency on Microsoft Visual C++ Runtime Package
(Microsoft.VCLibs.110.00) framework but is missing the framework
dependency declaration in the manifest.
My solution builds with zero errors. However, I receive an error after I create an app package and run the Windows Application Certification Kit.
I have added and removed references to the C++ runtime extension.
In addition, I do not see any fields in the app manifest editor to modify that would resolve this dependency error.
It sounds like you are including a library that was built with Visual Studio 2012. You will need to rebuild that library in Visual Studio 2013. If you just have the binary you will need to get an updated version from the author.
..
Or
Rename "Microsoft.VCLibs.110" to Name="Microsoft.VCLibs.110.00",
Or
Add a reference in your project to Microsoft Visual C++ Runtime Package
Add reference and find this Package. Adding this should resolve your problem