Are only universal windows platform (UWP) applications supported by Windows store or normal desktop applications such as win32 are also supported?
Also what is the difference between win32 project and a general empty project? is it the same but just with a console in the output?
Thanks in advance.
Are only universal windows platform (UWP) applications supported by
Windows store or normal desktop applications such as win32 are also
supported?
Currently the project types accepted by Windows Store include Windows universal apps for Windows 10 and 8.1 and Windows Phone Silverlight project:
For desktop application, only Win32 desktop apps using .NET 4.6.1 can be published to the Store via Desktop Bridge.
After you generate your converted package, you need to fill out this form and you'll acquire the permission to publish your package once your request gets verified.
Also what is the difference between win32 project and a general empty
project? is it the same but just with a console in the output?
You might refer to the response from #Elegentin Xie in this thread, which indicate the difference between them.
Related
I have a classical win32 Application in which I have a WMI call to get installed win32 application in the system.
I converted that win32 application into appx using Desktop App Converter.
The same WMI calls Works fine in the converted Appx. Normally in uwp we are unable to make WMI calls.
I don't know how those WMI calls are converted. Can anyone please explain?
Correct, The WMI calls is not available in the UWP app. When you convert your Win32 application to UWP app, you have permissions to access the WMI calls via the authorization.
A key goal of the Desktop to UWP Bridge is to separate application state from system state as much as possible while maintaining compatibility with other apps. The bridge accomplishes this by placing the application inside a Universal Windows Platform (UWP) package, and then detecting and redirecting some changes it makes to the file system and registry at runtime.
Converted app packages are desktop-only, full-trust applications and are not virtualized or sandboxed. This allows them to interact with other apps the same way classic desktop applications do.
So you can understand that the application packages it as an APPX and adds a UWP component. The app is still a win32 app.
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 heard that few of the Win32 APIs are not supported in Windows 8.1 phone. I have an c++ application which is using some Win32 APIs. How to check whether my application will work on Windows 8.1 phone?
You can find the list of supported Win32 functions on MSDN. However, since it can be hard to match supported functions with your code, you might as well try to compile the code yourself and check the errors (if any).
It mostly depends on what you were doing with win32. The list of functions is quite limited IMHO.
The best way is to run the WACK (Windows Application Certification Kit).
Right-click project, choose Store, then Create App Packages...
Say "No" to upload packages, then click Next
Select ARM & x86 release builds, then click Create
Click Launch WACK on the next screen
You might have to download a WACK update before you can certify (it changes pretty regularly as new APIs are enabled).
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.
I am developing a new application that will target the new WP8 platform.
Previous versions of Phone SDK, like WP7.1 or WP7.5 SDK contained special toolkit to test you XAP before submission for some obvious problems (like some mandatory image files missing).
A similar function is fulfilled by the WACK for Win8 Desktop Apps.
But I can't find any toolkit for testing my WP8 applications. The only option I found is to "Windows Phone Application Analysis" provides me with some performance information but there seem to be no static rule-based check of the XAP package performed.
Am I missing some software installation?
For WP8 apps, right click on your project in VS2012 Solution Explorer ---> Click "Open Store Test Kit". You can read more about what's being tested for on MSDN # http://msdn.microsoft.com/en-us/library/windowsphone/develop/hh394032(v=vs.105).aspx