Opened windows phone Emulator(start >> programs >> Windows Phone SDK 7.1 >> Windows Phone Emulator) and then trying to run Windows Phone 7 app in visual Studio 2010, this is trying to open new emulator, is there anyway to run the app in opened emulator (OR something like attach debug process)
-Edit:
my actual Problem is when i try to run on the emulator, it says "Error:Invalid or missing Rom image", and i found the solution on the net as "permanently delete .dess file under C:\ProgramData\Microsoft\XDE path" i tried this but no luck since there is no as such file. (but strange is that sometime back it was running properly :-p)
Open an instance of Visual Studio, add a Windows Phone specific project, and then run it. If the Windows Phone SDK was successfully installed, the demo app should run correctly inside the emulator. The emulator is opened automatically by Visual Studio, you do not have to start it manually from the folder it is installed in.
Related
I have a xamarin project and i want to debug it, but visual studio doesn't show any emulator or physical device.
this is the menu
I wanted to restart adb from tools > android but it's disabled. but when I open a non xamarin project (for example a web porject) this options is enabled.
I can see my device in cmd with command adb devices and in android studio, every thing is fine and I can deploy some java application to my phone.
do you have Any idea?
Update
I created new project and in this new project, every thing is fine and I can debug with my phone or emulators.
but in my existing project which I'm currently working on, there is no device in list.
It happened to me just now using vs 2019, to fix this, manually remove obj and bin folders restart vs, and that's all :)
is it possible to run react native app on Visual Studio Emulator for Android (standalone) and if yes what are the steps to set it up? I can successfully start emulator, that part works but cant figure out how to config react-native to use it instead of "adb devices".
My current attempts end with error:
Could not debug. Error while executing command 'adb devices': Command failed: adb devices
'adb' is not recognized as an internal or external command,
operable program or batch file.
I know about Android Studio and virtual devices that come with it but I would like to try that as the last option. My environment is: Windows 10 pro, VS Code (with React Native Tools Extension), react-native, yarn.
UPDATE
even though I did not get anywhere in my attempts to make it work
I just would like to share what knowledge I gained while struggling with this issue
because it is possible that my issues are specific to my environment but it might work on another PC.
Theoretically it requires very few steps to run react-native in Visual Studio Emulator for Android
in VS code without installing Android Studio or Visual Studio.
Install Visual Studio Emulator for Android, standalone
https://www.visualstudio.com/vs/msft-android-emulator/
download Android Debug Bridge (adb)
it is included with Android SDK Platform-Tools, download and read more here:
https://developer.android.com/studio/command-line/adb.html
it downloads as zip file, you unzip it and then add a path to adb.exe in PATH environment variable,
so you can execute adb command from any path. I am using yarn and it needs that to know where adb.exe is.
It is kind of a connector between your app and virtual or real android device
it has to be running before you start emulator and basic command are:
to stop - adb kill-server
to start - adb start-server
to see list of devices that adb recognized - adb devices
I also found a specific instruction on how to make Visual Studio Emulator for Android work with adb:
https://msdn.microsoft.com/en-us/library/mt228282.aspx
'Visual Studio Emulator for Android' devices are not listed in the Android Device Monitor
it is a registry edit for key
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Android SDK Tools
apparently Visual Studio Emulator for Android is using that and you can create it if it is not there
and just add/modify Path variable to be a path to adb.exe.
now you can start Visual Studio Emulator for Android and after that open integrated terminal in you react native VS code project
and type:
yarn run android
and if I get it right (and in the perfect world) your app should get installed and shown in Visual Studio Emulator for Android,
well, not for me, my emulator never shows up as a device when I type adb devices, all I see is a blank two lines.
So I think I spent enough time on this trying to make it work and in my case the answer to my own questions is:
theoretically you should be able to run Visual Studio Emulator for Android with react-native from VS code but in reality
it probably will not work, so seek something more reliable.
I did see a little light at the end of the tunnel when I tried connecting my phone with USB using expo app, adb picked it up right away,
"yarn run android" started doing something and expo even tried to load my app, I held my breath, my heart was racing, I was ready for a miracle... and .... boom... it just crashed, but this could be easier
for me to resolve though, it appears some networking config issues, my phone does not recognize IP address which was in the output after running yarn
and if this works,(big IF) then it is still good, I can run/debug react-native without using Android/Visual Studio.
Final update:
could not make it work, stopped all attempts and went for Android Studio instead, Android Studio emulators work with react native and expo without any issues. (well, not yet, sample app runs OK at least.)
The same symptoms occurred to me when trying to set both React-Native and VS Emulator for Android together, and the following steps solved them:
On the VS Emulator for Android, I checked my emulated phone's IP at the Tools/Network tab. Emulator Adapter #1 refers to the emulated phone.
Then, I headed to the terminal and ran adb connect <ip_address>:5555. That made the emulated phone available to Android Studio as well as to React-Native.
if you already install android studio
then add C:\Users\manu\AppData\Local\Android\Sdk\platform-tools path into environment path (replace your username instead of manu)
if you have not android studio then
need download adb from https://github.com/intel/haxm/releases/download/v7.0.0/haxm-windows_v7_0_0.zip
then install
intelhaxm-android.exe
.
open a new terminal and now adb commnad will work
it is haxm source website https://software.intel.com/en-us/articles/intel-hardware-accelerated-execution-manager-intel-haxm
Whenever I try to debug my UWP projects with the a one of the Windows 10 Phone emulators I get the following error after the emulator opens to the home screen:
DEP6100; The following unexpected error occurred during bootstrapping stage 'Connecting to the device '90F4E8F4-EC5F-4B64-B2E8-6EDE6F813BD3'.': SEHException component has thrown an exception.
The app never starts. I have not entered any code. I simply create a UWP app and then try to debug it with the Windows 10 Phone emulator.
I have already uninstalled and reinstalled VS 2015. I even did a windows 10 repair.
I get this the first time I debug an application. The trick I found is to do the following (precisely)
Make sure that your configuration settings are set to build and debug correctly (yes you need to check this UWP doesn't ship with it correctly configured)
Make sure the emulator is closed
Press the play button in visual studio
As soon as the emulator appears within visual studio, click on the build menu and hit cancel. This will stop deployment but the emulator will continue to boot.
Once the emulator has booted completely and you're able to navigate the OS, you're good to go. You can now run and debug your application normally.
NOTE: Don't close your emulator or you'll have to do this again. Just his stop in visual studio to stop debugging.
I'm trying to test a mobile website I'm building using Windows Phone 7, but I can't figure out how to do it. It seems that the SDK wants me to build an application first in order to use the emulator, but I'm not building an app, I simply want to test compatibility of my mobile site with windows phones. How do I do this?
If you install the free Windows Phone SDK you can run an emulator in standalone mode (i.e. without Visual Studio running).
Search for "Windows Phone Emulator" from the Start menu and just launch that directly.
Once in the emulator about the only thing you can do is launch IE Mobile.
(To enter URLs and other text using your real computer keyboard instead of the onscreen keyboard tap your "Pause/Break" to toggle keyboard mode)
You should be able to run emulator without building an app
try C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v7.0\Tools\XDE Launcher\XdeLauncher.exe
If now start visual studio and make an app f.e. Silverlight for Windows 7. Emulator will be loaded with debbuger attached. If you stop the app in VS, emulator should be still there. It has preinstalled IE which you can use to test.
Mind that it's better to test your web app on a real device.
I installed VS 2010 Express + WP7 SDK, it worked perfectly. Now I need to use unit-tests, and installed VS 2010 Ultimate (and reinstalled WP7 SDK). WP7 plugin seems to be installed (there are WP7 project types in "New Project" dialog), but when I'm trying to launch my software for debug, VS says that "Error 1 Zune software is not launched. Retry after making sure that Zune software is launched.". WP7 emulator is already launched (and Zune too, but Zune says, that there is no device connected). Expression Blend works with emulator perfectly (it runs the emulator by itself). Where is a mistake?
It seems like Visual Studio tries to deploy to a device.
Did you select "Windows Phone 7 Emulator" in the "Target Deployment Device" dropdown?
First of all, make sure that you have the Standard toolbar visible. That's where you select the Target Device. To do this: View -> Toolbars -> Standard. Since Expression Blend detects the emulator, then there is a problem with Visual Studio, that tries to deploy to a device by default.
REMEMBER: Zune Software is not required to be running when you are deploying to an emulator.
Second, try to create a new Windows Phone 7 project and try deploying it from Visual Studio to see how it works.