Windows 10: Deployment errors deploying UWP to Microsoft Windows Emulators

The UWP can be deployed to the Local Machine; the Simulator and the device Lumia 950.

The Hyper-V shows that the emulators are running. But it cannot be deployed to the emulators. Here are the error messages from two different version of emulators:





















:)

 

homescreen sample

If you want to run applications on your windows mobile phone that you have developed, to include the sample apps in the SDK, I would suggest that you use the emulator. This happens by default when you do a build and run and then you are prompted to select
an emulation mode. If you want to deploy the application to your actual device then you need to package your application into a .CAB file for deployment. I have written and developed a video tutorial of how to do this on my blog at this address:

http://techtips.timlaytonllc.com/2009/04/how-to-deploy-windows-mobile.html

 

Need help with combining Powershell with WDS

I use the MDT (Microsoft Deployment Toolkit) to accomplish this.

https://docs.microsoft.com/en-us/windows/deploy...

You combine MDT with the WDS

https://www.techrepublic.com/article/how-to-dep...

When you do that you can use the MDTs task sequence to generate a task that will allow you to drop scripts in during pre and post deployment.

 

Most probably you have selected wrong solution platform. For Windows Mobile emulators it should be x86, not x64.

 

I tried the x86 option as well since the error messages I posted indicated me in that direction. But I faced this new error.
'MainPage' does not contain a definition for 'Test' and no extension method 'Test' accepting a first argument of type 'MainPage' could be found (are you missing a using directive or an assembly reference?)

I do not have a button named 'Test' and I am not sure where it is coming from. The code shows clearly the following:
Fragment of code:
switch(connectionId)
{
case 1:
{
this.Test = (global::Windows.UI.Xaml.Controls.Button)(target);
}
break;
default:
break;
}
this._contentLoaded = true;
Somehow the code is not picking up the name of the button correctly. It should have been 'ClickMe'. I still wonder that the other deployments did not flag this error.