We just submitted app in windows 8 store (metro style app) and got the error:
XXX takes a dependency on Microsoft Visual C++ Runtime Package framework but is missing the framework dependency declaration in the manifest.
We had our app working fine in release version but it was not getting accepted as package so we needed to migrate our app as Windows RTM. During that we had following entry
in manifest:
<Dependencies>
<PackageDependency Name="Microsoft.VCLibs.110" MinVersion="11.0.0.0" />
</Dependencies>
If we keep this, we get following error while build the app.
Error : DEP0700 : Registration of the app failed. Windows cannot install package 5d6f272d-c915-4de1-a9d6-c0c08d63ab94 because
this package depends on another package that could not be found. This package requires minimum version 11.0.50727.1 of framework Microsoft.VCLibs.110
published by any publisher to install. Provide the framework along with this package. (0x80073cf3) Test_App1
So we removed it and submit the app, it just got failed and gave following error.
XXXX takes a dependency on Microsoft Visual C++ Runtime Package framework but is missing the framework dependency declaration in the manifest.
We need to keep this package itself in the manifest but not getting it done.
I had similar problem.
Add a reference in your project to Microsoft Visual C++ Runtime Package
Just click on project i select Add reference and find this Package. Adding this should resolve your problem
The issue got resolved by updating
"Microsoft.VCLibs.110" to Name="Microsoft.VCLibs.110.00"
Just I've repaired the VS 2012 for windows 8 from Control panel > Programs and the designer works fine.
Related
Using NuGet Package Manager, I get this error message:
Could not install package 'Microsoft.Toolkit.Uwp.UI.Controls 3.0.0'.
You are trying to install this package into a project that targets 'native,Version=v0.0',
but the package does not contain any assembly references or content files that are compatible with that framework.
For more information, contact the package author. 0
The app is a Blank App (C++/winRT). Visual Studio 15.8.0 Preview 4.0.(10.0.17134.0, 10.0.17704.0)
Despite it's name, the Windows Community Toolkit is only intended for C# developers.
I haven't had problems with nuget until now, i created a blank a UWP project and decided to add some few nuget packages to it and it keeps saying 'Package restore failed. Rolling back package changes for App1'. But when i do this a WPF project it successfully install. Does anyone here knows why this is happening or is also ?
I ran into the same problem with other packages. The problem is that many NuGet packages don't seem to be compatible with UWP. This incompatibility info is shown in the output console rather than the error console of Visual Studio.
See also .NETcore, UWP - can't install NuGet package.
I created a new ASP.NET 5 preview project in VS 2015 RTM (fully updated). When I try to debug it, it fails with the following exception:
The current runtime target framework is not compatible with
'ProjectName'.
Current runtime Target Framework: 'DNX,Version=v4.5 (dnx45)' Type:
CLR Architecture: x86 Version: 1.0.0-beta6-12256
Please make sure the runtime matches a framework specified in
project.json
I went with the default settings in the new project dialog, which I believe included a dependency on .NET 4.5.1 (though there's no mention of that dependency in the project.json file - contrary to what the exception message claims). I tried the solution offered here (defining the DNX_IIS_RUNTIME_FRAMEWORK environment variable in the project's debug settings) without success.
Install latest tools and try again. Beta 6 isn't apt to be supported and lots changed since then. You can get the tools here: http://www.microsoft.com/en-us/download/details.aspx?id=49442
I'm trying to add 'Microsoft Office 365 Mail, Calendar and Contact Library' package to a project on Xamarin Studio for OSx and get the error :
Adding Microsoft.Office365.OutlookServices...
Attempting to resolve dependency 'Microsoft.OData.Client (≥ 6.8.1)'.
Attempting to resolve dependency 'Microsoft.OData.Core (= 6.9.0)'.
Attempting to resolve dependency 'Microsoft.Spatial (= 6.9.0)'.
Attempting to resolve dependency 'Microsoft.OData.Edm (= 6.9.0)'.
Downloading Microsoft.Office365.OutlookServices 1.0.22...
Object reference not set to an instance of an object
All of the dependencies listed above are installed and other Microsoft packages such as 'Microsoft Authentication Library' were installed successfully.
Any solutions would be helpful. Thanks.
It seems to be a problem with Mono failing to resolve the portable library folder which is using %2B instead of +
portable-net40%2Bsl5%2Bwp8%2Bwin8%2BMonoAndroid10%2BMonoTouch10%2BWindowsPhoneApp81
The NuGet package works fine with Xamarin Studio on Windows.
There is a similar problem with Mono.Data.Sqlite.Portable 1.0.33 where it was using %2BXamarinMac which seemed to be incorrectly being resolved to a part in the zip file. To fix the Mono.Data.Sqlite.Portable NuGet package the Xamarin frameworks were removed from the portable library folder inside the NuGet package and that fixed the problem. I suspect it could be fixed by changing the %2B to + in the NuGet package.
I think you can use the Microsoft Graph.
I'm working on a WinJS app which works perfectly on one particular Windows 8 image, but will not deploy on another that we use.
Attempting to run any WinJS project from visual studio results in the following error:
Error 1 Error : DEP0800 : The required framework
"C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0\ExtensionSDKs\Microsoft.WinJS.1.0\1.0
\Microsoft.WinJS.1.0.appx" failed to install.
Deployment Add operation on Package Microsoft.WinJS.1.0_1.0.9200.20602_neutral__8wekyb3d8bbwe
from: ([path]) failed with error 0x8007065E. See ]link] for help diagnosing app deployment
issues.
Attempting to sideload the app doesn't work either, producing a similar error about the WinJS dependency not being resolved.
Any ideas?
Try changing the package identifier in the manifest and see if that helps.
Is this the application already on the machine? When updating an existing application, I've run into this a few times and first uninstalling from the target machine and then deploying from VS works.