While I was on vacation, I prepared the next episode of our Windows Store Apps Development series has been published.
You’ll find demos, code and tools to help you write better Desktop applications with WinRT!
Enjoy!
Advertisements
While I was on vacation, I prepared the next episode of our Windows Store Apps Development series has been published.
You’ll find demos, code and tools to help you write better Desktop applications with WinRT!
Enjoy!
Thanks a lot for this fine explanation.
for my desktop app using Mobile Network Operators API I can get the privileges, when I can tell them what they have to do. For Windows Store apps this is well documented (metadata). But what have to be done for a desktop app using this interfaces?
Thank you
Ferdinand
Hi Ferdinand,
I’ve explained this topic into https://iinspectable.wordpress.com/2013/08/18/dualapi-finder-or-listing-winrt-types-usable-by-desktop-apps/ and http://blogs.msdn.com/b/mspfe/archive/2013/09/24/winrt-for-desktop-apps.aspx
Hi Christophe,
Thank you. Yes, I have now a console application that try to send a USSD message and gets always just terminated (Windows 8.1). In Windows 10 enumeration of network adapters already returns 0. I guess its because my demo app just runs out of Visual Studio and is not signed and does not have special magic (Mobile Network Operators privileges). Is there a way to test the app before I ask the Mobile Network Operator to run through all the signing steps like required for Windows store Mobile Network Operators apps?
I don’t know this API… What does MSDN specify for its availability? Is it supported for desktop apps?