将参考从Microsoft.Phone.WinJS.2.1,版本1.0.9651.0更新到版本1.0.9651.40228

时间:2014-08-12 21:09:24

标签: visual-studio-2013 windows-phone-8.1 winjs project-reference

我正在使用Update 3在Visual Studio Professional 2013中构建/部署我的Windows Phone应用程序。以下控制台输出显示:

1>------ Build started: Project: CapturingVideos, Configuration: Debug ARM ------
2>------ Deploy started: Project: CapturingVideos, Configuration: Debug ARM ------
2>Deploying to Phone Internal Storage...
2>Creating a new clean layout...
2>Copying files: Total <1 mb to layout...
2>Checking whether required frameworks are installed...
2>Warning : DEP0810 : This app references Microsoft.Phone.WinJS.2.1, version 
1.0.9651.0, found in your SDK, but you have a higher version of 
Microsoft.Phone.WinJS.2.1 installed on the target machine, 1.0.9651.40228. If you 
continue to run this application, it will run against the currently installed version,  
Microsoft.Phone.WinJS.2.1, version 1.0.9651.40228. Consider updating your SDK to match     
the version of Microsoft.Phone.WinJS.2.1 that is installed. 
http://go.microsoft.com/fwlink/?LinkId=260891
2>Registering the application to run from layout...

我很好奇警告,它建议我将WinJS.2.1 v1.0.9651.0的引用更新为v1.0.9651.40228。所以我下载并安装了Visual Studio 2013 Extensions for the Windows Library for JavaScript。重新启动操作系统和VS 2013后,我尝试从空白模板创建一个新的Windows Phone项目。我希望References文件夹包含Windows Library for JavaScript 2.1 v1.0.9651.40228。但是,它仍然只指向旧版本,即v1.0.9651.0。我是在错误的轨道上还是我错过了什么?请指出正确的方向。谢谢!

2 个答案:

答案 0 :(得分:2)

问题是由错误的应用程序包版本号引起的,尽管包含的所有.js和.css文件都具有正确的内部版本号,但在引用属性中显示为 1.0.9651.0 在其标题中指定了strong> 1.0.9651.40228 。

App Package Version属性从包的清单文件%Program Files%\Microsoft SDKs\WindowsPhoneApp\v8.1\ExtensionSDKs\Microsoft.Phone.WinJS.2.1\1.0\SDKManifest.xml中获取其值,特别是来自以下行:

FrameworkIdentity="Name=Microsoft.Phone.WinJS.2.1, MinVersion=1.0.9651.0"

请关闭文件的只读标志,以管理员身份打开并更改MinVersion号码。重新加载您的解决方案。警告信息应该消失。

答案 1 :(得分:0)

我遇到了同样的问题,并在StackOverflow上发现了这篇博文,以及您的问题:

http://blogs.msdn.com/b/lighthouse/archive/2014/04/21/can-t-update-visual-studio-2013-extensions-for-the-windows-library-for-javascript.aspx

我没有描述您所描述的问题,或者在博客文章中提出过警告的问题,但他们解释了如何使用PowerShell脚本纠正这些问题。