I have started to explore the Universal Windows Platform, and saw at the Windows 10 SDK download page:
The Windows 10 SDK allows you to build Universal Windows apps as well as desktop apps for Windows 10, version 1607.
If I build an app with this SDK, will it work on future versions of Windows 10?
This is from the page that lists all Windows 10 version 1607 API changes:
Many runtime APIs have been added or changed in Windows 10 version 1607. This table lists the namespaces that have been added or changed in this release. [...]
When browsing the classes, you can see notices regarding this. For ex., several members of the class Windows.Media.Playback.MediaPlayer have this notice:
MediaPlayer.[MemberName] may be altered or unavailable after Windows 10, version 1607. Instead, use [...]
So I don't get it. No more backward compatibility? If I build an app for version 1607, may it break after the user update Windows 10 to the next version? Or will it work, but my code become "obsolete"?
Think of it as making an app for Android: Your app can work as long as Google doesn't break the interface. Usually when they change something, they give you time (by the message kind of "MediaPlayer.[MemberName] may be altered or unavailable after Windows 10, version 1607. Instead, use [...]") to update your app.
UWP app for Windows 10 is no different in that scene.
If I build an app with this SDK, will it work on future versions of Windows 10?
Yes. If it will not work, then they will tell you explicitly that it won't work in version xxxx. Now they are using the word May be.
Related
I can successfully run a windows 8.1 store app without any issues however I cannot get it to work with assigned access on Windows 10. Is it even supported? or do I have to migrate the app to a UWP app?
On one of my windows installation it doesn't even appear in the list of available apps. On another installation it appears as an app but just immediately exits when the application starts.
Try to set assigned access for windows 10 application (not for Windows 8.1 app). Yes, it is supported on Pro, Enterprise and Education versions.
You can set it by different ways like it described in this topic:
Set up a kiosk on Windows 10 Pro, Enterprise, or Education
I am having windows phone 8 silverlight app. I need to publish it on Windows store. Can you please provide or explain step by step guide to publish this app in store.
Stackoverflow link discussed already. But after changing the values in files manually what need to do after tha?
I followed the steps mention here, but i am getting certification issue after submitting app.
This is a guide to publishing applications in Windows Store. Important -Silverligth app supported only Windows Phone and not supported Windows 8 and Windows 10. For supported Windows RT you need to make migration to universal app.
Windows App certification kit is very nice utility. Before publishing app use this app for analysis. When i run analysis of my XAP file using this utility, I found that i was using some default images that was main issue in certification failure. Now i am updating that. And will let you if this works or not.
I've been working on a Windows Phone 8 app, which I now want to change to be Windows Phone 8.1. How can I do this?
Should I create a new Windows Phone 8.1 app and copy all my existing files into it? Or is there an automated way for me to upgrade the existing solution to 8.1?
There are two ways to do that:
like in comment - right click on oyour project and you should see Retarget to Windows Phone 8.1
or you can open Properties window of your project and the in dropdown box Target Windows Phone OS version you can choose Windows Phone 8.1
In every case the VS should ask if you are sure to do that - it's one-way operation, so it's worth to make a backup of your solution. As WP8.1 has backward compability, in most cases there shouldn't be any problems.
Some clarification for the followers:
As WP8.0 apps are Silverlight, after retargetting it will still be a Silverlight app but WP8.1 (some new features and enhancemens).
Thought, if you want to retarget to WP8.1 Runtime, it's a totally different thing - it's a different type of an app, different API and more. You will have to port it manually. Note that not all features from WP8.0 are yet available in WP8.1 Runtime - here is a good article about that.
I have been using Windows 8.1 for creating Windows Store apps. Below is output of winver command.
I have installed necessary updates to start developing universal Windows Store app using JavaScript. When I try to launch app on Windows Phone emulator, I am getting following error.
Unable to start windows phone emulator
It also suggesting to use Windows 8 pro version. Is there anyway of running this without requiring to throw more money on getting Windows 8 Pro version?
Windows Phone Emulator requires Hyper-V which needs Windows Pro version. That's probably why you aren't able to start your Emulator.
As I've posted in comment, I've heard about VirtualBox and an ability to run WP Emulator on it. Some helpful links: other question on SO, VirtualBox forum, video. I'm not sure how it will work (and if) as I haven't tried this.
IMO I would follow WiredPrairie's comment - upgrade or buy inextensive phone.
For now in windows RT it is possible to access D3DCompiler.h, but application will not pass the store test (this is corrected in windows 8.1).
Is there a way to add D3DCompiler in windows phone project? (Mostly I need reflection support, shaders are generally precompiled). I tried to add the ARM build reference but it doens't seem it wants to include it (some xap security?).
Please note that for now I don't need store deployments, so if it works for development purposes that's fine (and either c++/sharpDX solution is pretty welcomed).
D3DCompiler was not available for 'production' use with Windows Store apps for Windows 8.0 or Windows phone 8.0. It was available for development, but the D3DCompiler #46 DLL itself will not pass the WACK tool for submission to the store.
It is available with Windows Store apps for Windows 8.1 and Windows phone 8.1. The D3DCompiler #47 DLL is included as part of the OS now. See this blog post.