I have a developer unlocked Lumia 635 just yesterday updated to Windows 10 Mobile Technical Preview (OS version: 10.0.12562.84).
After
Ok, I've managed to finally deploy this sample app to the Windows Phone 10.
In your project's Package.appxmanifest change the MinVersion
from "10.0.10069.0" to "1.0.22816.1" (unexpected, hah?) like this:
After you'll build the project just created from new "Windows 10 Universal Blank App" template in VS2015 RC the original Package.appxmanifest available from solution explorer in Visual Studio will copied to YourBlankWin10PhoneProject\bin\x86\Debug\Core\AppxManifest.xml
(notice the Core subfolder in the path) and updated with new dependency - .NET Core Runtime package:
(Don't confuse with another copy of the original unmodified version of the manifest at YourBlankWin10PhoneProject\bin\x86\Debug\AppxManifest.xml
)
As you could see MinVersion
for both dependencies is different and the application's one is greater then the Core Runtime component's. Now if you update MinVersion
in the original Package.appxmanifest from the solution explorer to match the MinVersion
of the Microsoft.NET.CoreRuntime.1.0
package, i.e. to 1.0.22816.1, next time you'll build the project the Core copy of the manifest will be updated accordingly:
Now application should be deployed to the phone without problem.
PS. Found the hint to solve this in Deep Dive into XAML and .NET Universal Windows App Development video, fast forward to 0:19:50.