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.
Related
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.
I'm trying to set up continuous integration testing for a Windows Store (8.1) app on Visual Studio Team Services (formerly Visual Studio Online).
Setting up build was fairly easy, but I have not been able to get it to run my unit tests on a Hosted Agent. So far I have:
Added /t:Publish to the build to produce the test runner .appx
Created a Powershell script to install the appropriate certificates onto the agent
Modified the test search path to find the .appx
Now, I'm getting errors about installing a developer license:
Error: Could not start test run for unit tests for Windows Store app: No valid developer license found for running unit tests for Windows Store apps. Please install/renew your developer license..
It does not appear to be possible to add a developer license strictly from Powershell or Command Prompt, so is there some other way of running the tests on a Hosted Agent?
Assuming you are using vNext build and Universal Windows Platform template by following this article.
As the developer license is deprecated in the Windows 10 operating system, Universal Windows Platform template doesn't require developer license. But if the computer that hosts the build agent will be used to perform unit tests for windows 8.x, developer license must be installed on the computer.
So, there is no way to run tests for Windows 8.1 on Hosted Agent. You need to deploy a Windows build agent or set up an on-premises build controller + build agent to test Windows 8.1 application.
I have deployed my UWP application to windows store successfully. It rans perfectly in windows phone, however, when installed in pc / laptop from windows store, it fails and crashes.
checking event viewer (windows log) shows below error;
Activation of app
AppName!App failed with
error: The remote procedure call failed. See the
Microsoft-Windows-TWinUI/Operational log for additional information.
I didn't understand what kind of error it is?
Thanks!
Have you tried yourself, with Visual Studio 2015, to run it on a Windows Phone device in Release Mode ?
Most of time, this kind of errors are due to .NET Native, which is not activated by default on Debug build but which is activated when app is published on the Store.
Thanks,
Does your app reference a portable project? If yes, does the referenced project include resource files? We have encountered similar issues and they were related to resource files. Everything worked nicely when the app was manually deployed but when downloaded from Store, the app just didn't work.
Turns out the problem was with the resource files which were inside referenced project. The problem was solved by copying the resource files from the referenced project into the app's project.
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).
I am very new to mobile application development. Now I am into a mobile application project which should work on IOS, Android, BB and WP.
After googling to learn what can I do on this, I felt Phonegap fulfils my requirement. I have downloaded and installed phonegap on eclipse to start develop for Android.
I have downloaded, SDK, AVD, eclipse etc to get started with Phonegap for Android.I followed the procedures in the Getting Started Guide.
For User Interface, I took Intel App Framework as my tool of choice.
Everything goes fine with me, other than my doubts in Cross Platform mobile application development.
1) I have read about PhoneGap build, it just requires html,css and js file to wrap up an application for different platforms. So downloading and linking phonegap.js in an the application is not required unless I need to access the device's native function ?
And just create a responsive HTML5 application and build with PhoneGap Build is all I have to do ?
2) If I can just do like above, then why I should install eclipse and android SDK to create for android when I can just make HTML5 application and build with phonegap build and put it on google play.
3) I have came across Intel XDK and they have similar service like phonegap, if I use Intel XDK then I don't have to use any assets of phonegap ?
Please answer these question as these things are confusing me a lot.
As per my knowledge these are the answers,
1) I have read about PhoneGap build, it just requires html,css and js
file to wrap up an application for different platforms. So downloading
and linking phonegap.js in an the application is not required unless I
need to access the device's native function ?
Yes, until your application need to access devices's native function or any inbuilt or custom plugins, no need of phonegap.js.
And just create a responsive HTML5 application and build with PhoneGap
Build is all I have to do ?
2) If I can just do like above, then why I should install eclipse and
android SDK to create for android when I can just make HTML5
application and build with phonegap build and put it on google play.
Phonegap applications need to be developed as native applications using web technologies,
ex: IOS apps need to developed on MAC (using IOS SDK) etc.
3) I have came across Intel XDK and they have similar service like
phonegap, if I use Intel XDK then I don't have to use any assets of
phonegap ?
Intel XDK using cloud based development where your html,css etc are uploaded into the Intel server and the application will build their and give your the final build. In this case you no need of MAC for IOS application development.
In my experience developing with Phonegap and its Build service I generally use a plain web IDE which is based on eclipse called Aptana. It's primary use is for just HTML web development. I never install iOS or Android SDK's since the whole reason you use Phonegap's online build service is so you can be free from having to set up multiple development environments.
All my project specifications are configured in the config.xml. I don't include a copy of Phonegap's libraries since they are bundled at the time of compilation in via Phonegap's online build service.
For general testing and debugging I use either the Chrome debug inspector or Chrome and the Ripple emulator. When I've finished testing and need to compile the binaries I send my code up to Phonegap's build service using maven and Chris Price's Phonegap build maven plugin.
This allows me to :
Unlock the signing keys (maven-ant-plugin and an http get call)
Upload my project for compilation to Phonegap's Build service
Sign my project with a specified signing key
Download a compiled binary for a specified platform
All from one single command. When I develop on my Mac Mini I installed a ruby script which will deploy the downloaded binary straight to my iOS device as final step.
I came up with this solution with the idea that I wanted to be able to checkout my code and be able to compile it online using only maven on any machine. This achieves that.
To answer #2. For phonegap you only need to download eclipse and android SDK or Xcode(iOS) if you are NOT using phone gap build. If you use Phonegap Build (included with Photoshop subscription) you can build with their servers and download the app straight to the device through the phonegap site. Its real simple for Android, a bit harder for iOS.
My understanding is that you have to subscribe to iOS Developer Program (US$99pa) to generate an iOS-installable app (even just for testing it), and publishing/distribution is also a bit more complicated than e.g. Android as well. That is completely regardless of what tool you use to build it, you need an Apple key code to install it. Of course, you can always just build and publish it as a a web application that be viewed in any browser. Then you don't need the iOS developer sub.