I have a Windows 10 Desktop application that needs to use a Windows Runtime API.
Solutions I tried:
Enabling Windows Runtime libraries from within my Windows Desktop application – the API was available but failed;
using the API in a Windows Runtime background task. There I have not found a reliable trigger so far. The best would be to trigger the background task from my Windows Desktop application.
start the Windows Runtime App from Desktop application using the IApplicationActivationManager – works fine, but the suddenly popup of an screen that disappears after few seconds will annoy the customer;
For solution 2., Is there a way to trigger a Windows Runtime background task from my Desktop app?
Issue solved by using AppServices, see https://msdn.microsoft.com/de-de/library/windows.applicationmodel.appservice.aspx
Related
Downloaded and loaded Windows 10 Pro (X64) via Parallels Desktop and attempted to download Desktop App Converter but wasn't able to do so as I was receiving a message stating "This app will not work on your device."
On scrolling down I could see that the issue was caused due to the fact that the Store did not detect that my OS was running in X64 architecture, but it was ! (as seen in the screenshot)
I contacted the Microsoft support team, explaining this. A tech representative took control of my desktop and figured out that the issue was that I was running Windows 10 as a VM on a Mac.
The work around is to install the Desktop App Converter from https://www.microsoft.com/en-us/download/details.aspx?id=51691
I've been developing a Windows Phone 8.1 app using C#/XAML. My configuration is up-to-date Windows 8.1 PC + Visual Studio 2013.
I can test my app on WP 8.1 emulator that comes with VS2013, and also no problem deploying it on physical Windows 8.1 device.
However the app also runs on Windows 10 Mobile because the platform currently allows it that way. Which is good except, my app doesn't work as intended since the device got Windows 10 Mobile Anniversary Update.
I don't know if the problem is in Windows or in my app but that's not important here.
I need to create a hotfix for the issue. And here comes the question. Is there a way to deploy WP 8.1 app to Windows 10 Mobile without submitting it to the store first, without upgrading to Windows 10, and preferably without upgrading to VS2015?
UPDATE The reason I want to deploy WP 8.1 app to Windows 10 Mobile is to test if my patch fixes the issue manifests with Windows 10 Mobile. At the moment I don't understand where is the problem and keep submitting the fix attempts to the store is not ideal.
Thanks.
Is there a way to deploy WP 8.1 app to Windows 10 Mobile without submitting it to the store first, without upgrading to Windows 10, and preferably without upgrading to VS2015?
Yes, it is possible to deploy WP8.1 app to the Windows 10 Mobile without submitting it to store and without upgrading to Windows 10 and without upgrading to VS2015. But you need to make sure you have the Windows 10 Mobile device for you to test.
If the Windows 10 Mobile device is in your side, you can unlock the Windows 10 Mobile device and deploy your app to the Windows 10 Mobile device by using the USB with the same method that you deploy it to the Windows Phone 8.1 Mobile device.
Or you can try to sideload your app on the Windows 10 Mobile device without submitting it to the store by using the Application Deployment tool. For more information, please try to refer to this article:How to deploy Windows Phone 8.1 apps with the Application Deployment tool.
Whenever I am starting to test an Windows Phone app (even a blank app) on emulator, I am getting error "The project needs to be deployed before it can be started". The emulator will be started & run successfully, still no luck in deploying app on emulator. Getting error DEP6100 & DEP6200.
These are the stuffs I tried till now:
Checked "deploy" option in 'Configuration Manager'.
Tried deploying Windows 10 Mobile, Windows Phone 8.1 & Windows Phone 8 blank apps on different types of emulators.
Although I am able to run apps on my device.
I am running Visual Studio Enterprise 2015 on Windows 10 Enterprise.
The Emulator is x86 based and Phone is ARM architecture. To run the app in the emulator, change the CPU to x86 in the toolbar and compile it. Now you can deploy te App to the Emulator and test it.
I faced problem like that and I fixed it by right click on project > properties > change platform target to X86.
I just started playing with Xamarin Forms, and ran into this error after following the Xamarin Forms Quickstart Guide. The error message actually said to Run the Deploy... for the project that you are trying to run. Deploying the project seems to install some Windows dependencies that might be required to run the UMP. After deploying the project, it ran without issue as a Windows Desktop app, or if you change to Device, then install emulator, as Windows Phone app.
This error was relentlessly happening to me as well, and I found out that it was because my project was saved on a SanDisk SD card. If I simply moved the entire solution to my C drive, it built without issue, but on the D drive, it would give this error.
I just downloaded the universal app background task sample application for windows phone 8.1 and windows 8.1.
http://code.msdn.microsoft.com/windowsapps/Background-Task-Sample-9209ade9
So after going through the code, I understand that the background task is being implemented using the windows runtime component. I am trying to use the timertrigger.
Is it a possibility that the background task be implemented using the Silverlight 8.1 windows phone project instead of a windows runtime project?
The answer above is wrong. Wonder how it has 5 votes. Anyways, background task cannot run in a silverlight applciation but it can only register a background task. It has to be a runtime project that runs a background task.
A silverlight application can just register a background task which is a separate runtime project. Its a different process all together.
Yes, it is possible. The reason why they chose a Windows Runtime project in this example was to show the new Universal Apps. You can use the BackGroundTasks in a Silverlight based project and in a Windows Runtime base project.
But if you ever plan to expand you app to Windows 8 you should think about making it a Universal App.
I installed Windows 8.1 RTM and installed VS2012 had a little problem while installing windows phone 8 sdk but i guess it is resolved now but still i have a weird problem.
Even i select "device" as the launch target when clicked the run button VS launches the app on the emulator not the phone. Surprisingly if i right click the project on solution explorer and select debug it this time launched app on the device.
Is there anybody faced with this kind of problem? I dont want to install everthing from scratch :)
Ok it was my fault, since the project build platform was x86 visual studio could not deploy the app to the device and hence launching the emulator. When i changed the build platform to Any CPU now it deploys my app to the device without any problem.