Is there a way to allow a normal Windows 10 installation to run Windows 10 IOT apps for debugging purposes?
Right now when I set the architecture from ARM (Raspberry Pi 3) to x64 (Local machine) I get the following error message when I start a debug session:
I've read here that it's got something to do with 'embedded mode' but I can't find any information anywhere about it and the group policy does not appear to contain anything about enabling embedded mode...
Help is greatly appreciated! Thanks in advance!
It turns out that in addition to applying the policy, you also have to start the "Embedded Mode" windows service:
After that, everything works flawlessly. Just make sure to change ARM to x64 or x86.
In addition to enabling the Embedded mode service, and you find the service cannot be started manually, one will need to run a provisioned package on the OS other than Win IOT Core that will set AllowEmebeddedMode = 1.
Download the Windows 10 ADK
Install it
Build a package
Run the package
The embeddedMode service should run automatically.
More info here.
I'm not sure what you mean with a Windows 10 IoT app if you don't mean an UWP app, and that should be able to run on your PC. Have you activated Developer Mode on your PC? If not, got to System → Update & security → For developers and choose Developer Mode. This will let you run all UWP apps, and not just those from the Windows Store.
Related
I made a new Xamarin Project in Visual Studio , I chose the Single View App .
Then I did not make any changes.
I just pressed the Run Button.
The emulator started ,
but the app was not appeared in the menu of the phone of the emulator.
Is there anyone who know what cause the problem?
On Windows you have a couple of options to accelerate the Emulator. Read more here: https://learn.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/hardware-acceleration?pivots=windows
Using HyperV: Make sure to install the Windows Hypervisor Platform:
Right click on the Windows button and select ‘Apps and Features’.
Select Programs and Features on the right under related settings.
Select Turn Windows Features on or off.
Select Hyper-V and click OK.
You probably need to restart your computer after.
Intel HAXM: If you are not using HyperV and don't intend and don't run other hypervisors such as VMWare, VirtualBox etc. then you can install Intel HAXM.
In the Android SDK manager, in tools, download Intel HAXM. After that is done, go to the folder where the Android SDK is installed. There should be an extras folder where there will be an installer for Intel HAXM.
On macOS, Intel HAXM is the way to go. Read how to install it here: https://learn.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/hardware-acceleration?pivots=macos
Should be as easy as running sh ~/Library/Developer/Xamarin/android-sdk-macosx/extras/intel/Hardware_Accelerated_Execution_Manager/silent_install.sh from a command-line.
Either of these approaches should significantly speed up the Android Emulator.
If you have issues deloying to the emulator, sometimes the default configurations have very limited space and installing anything may fail due to the emulator running out of storage. Go to the Android AVD and increase the internal storage size.
For other failures, check the Deploy Output window in Visual Studio and provide more information of what is going wrong. Otherwise it is just a guess.
This might be just a bug. Create a new project. If still blank wait 5 minutes. Maybe your computer is slow so it takes time to load.
If you start using xamarin for the first time
Create device from dropout menu (don't just let it create it from pressing run button).
Select device from dropout menu.
Run up.
if it didn't added just restart Visual Studio (should change "Run" into name of the device)
I'm trying to build an application for windows phone 8 on visual studio 2012 using windows 10 pro - 64-bit.
WP8 SDK with last update and VS2012 update 4 have been installed.
An error appear when i run app:
also an error appear on console: 0x80131500
I checked the hyper-v, and nothing relate to WP8 emulator was there!:
Please follow these steps to make sure the Hyper V service is installed and turn on.
How to Setup and Use Hyper-V in Windows 10 for OS Virtualization
Pay attention when it comes to enabling the service with this picture.
I'm pretty sure a computer reboot is required. If that still doesn't work for you then you have something conflicting with HYPER-V or your hardware does not support it.
I know VM Ware does not play nicely with HYPER-V turn on and vice versa, so you might want to build a separate computer for your Windows Phone development like I did, if you run VM Ware Player or Workstation.
Recently i encounter the same problem, it turns out that you have to install windows phone 8.1 sdk in order to run windows phone 8 app unter windows 10. Surprised ?... me neither :D
In the last updates of Windows 10, is possible that MS pushed one to prevent using the Windows Phone 8.0 SDK (the one that uses VS2012). My recommendation: create a Virtual Machine in VMware with Windows 8 or Windows 8.1 and install the SDK.
I'm developing mobile application for device running windowce CE. I'm trying to get my app started on windows CE emulator. On the emulator i have installed net compact framework 3.5 and compact sql. My app also installes from cab succesfully but when i try to run my app nothing happens. No error message or anything.
I have tried not deploying my app from cab but just copying files over to emulator but no use. In device it is working but i'm not always able to use the device when i need to run my app for testing.
Maybe someone has idea what to look or try.
Did you try to run it on the debugger?
It may be that the app is accessing some API or some driver that is not supported by the emulator and this prevents it from starting.
Starting in the debuger you may be able to step trough the main rountine or, at least, will have a chance to see some debug messages.
Is the Windows CE emulator running the same processor type than the real device? In contrast to Windows Mobile 6.x, Windows CE can also run on x86 instead of ArmV4i (XScale).
Did you really install the correct CF runtimes?
If you are running the stand alone device emulator there is an option to dock the emulated device and then use simply ActiveSync or WMDC. TCP/IP (viw emulated network) with emulator will no more work on Windows 7 PCs, the driver cannot be installed.
If the above does not help watch the Visual Studio Build window when you deploy a debug version of your app. VS will then deploy all necessary CAB and DLLs to the device.
I developed a c# software using windows 7. IDE is Visual studio 2010 professional, and the only dll it use is speech.dll. I generated an installer using the default way build menu->publish _software name_ -> Finish, when the setup wizard is on.
I provided the whole publish folder into 2 computers, windows 7 and windows 8. App installs fine in both machines but when it is about to run, windows 8 is saying Windows SmartScreen prevented an unauthorized app from running
Why is this happening? Please help!
Windows 8's SmartScreen is designed to "protect" consumers from malicious programs. In order to be trusted, you need to either buy a cert or sign up to distribute your application through the Windows Store (which costs less money).
It's a terrible move by Microsoft and will hurt devs like you, but there's currently no way around it. You will need to press "More information" when the SmartScreen alert comes up and then press the "Run" button to let your application run.
I need to get an information about whether my app is running on x86, x64 or an ARM device.
is there any way to get this information in a windows 8 app via the windows runtime API.
Thanks
// Miro
You can call GetNativeSystemInfo from a WinRT app. That tells you the architecture of the underlying device.
While the app is running, go to Task Manager and select the app. Then right-click and select the file location. If it is installed in the program files(x86) folder, then it is a 32bit app. Otherwise it is an x64 bit app.