I want to develop an application in Visual Studio 2015 on my desktop
and run/test it on my Surface 3.
I created a Blank application (Universal Windows) and I can run it on “local machine” but when trying to run it on “Device” I get the following error
Error DEP6200 : Bootstrapping failed. Device cannot be found. 0x89731810:
Deployment failed because no Windows Phone was detected.
Make sure a phone is connected and powered on. App1
Both are running Windows 10 version 1511 (Build 10586.164).
The surface is connected with USB.
The developer mode on the Surface 3 is activated.
IpOverUsbSvc is running on the desktop.
Note that I don’t seem to find the Surface 3 in the Device Manager
and when I plug it in, no attempt seems to be made to install drivers.
This is probably the root cause so any advice to let "Device Manager" recognize the "Surface 3" would be appreciated
To debug on a remote device such as a Surface 3, you need to install the Remote Debugging tools for Visual Studio 2015 then select the "Remote Machine" option, the "Device" option is reserved for Windows Phone and Windows 10 Mobile devices at the moment
Related
I have some old windows 10 mobile phones, that I want to give a second life as a music device for my kids. Since I have Visual Studio 2019 Enterprise at my hands, I thought I try to create something myself.
Not I tried to create an UWP app and a Xamarin app and try to debug them on the phone (connected via USB, developer mode enabled, unlocked). But with both I get this error:
DEP6957: Failed to connect to device '127.0.0.1' using Universal
Authentication. Please verify the correct remote authentication mode
is specified in the project debug settings. COMException ... HRESULT:
0x8007274D) [0x8007274D]
The apps are still in their initial state after creating the project, no modifications done. The settings for debugging are set to: Debug, ARM, Device
I had some experience with an older Visual Studio version and windows phone 7, back then it just worked and all the documents I could google up suggest, while there are new ways, it should still work via USB.
If you plan to develop Windows 10 Mobile App, you need to use Visual Studio 2017 and make sure the target version of the app is below 14393.
Visual Studio 2019 no longer supports deploying UWP apps on mobile phones.
Best regards.
sometime i must reboot service something like windowsphone ipoverusb
I'm developing a UWP app for Windows 10 Phone. Since some days when I try to deploy the app from within Visual Studio I get asked for a PIN in order to connect to the device
In the phone settings I can trigger pairing so a new PIN is generated for me. But when I enter that PIN, a new dialog appears telling that the PIN was wrong:
If I press 'Cancel' then the deployment is interrupted with an error message:
1>Error : DEP6100 : The following unexpected error occurred during bootstrapping stage 'Connecting to the device '30F105C9-681E-420b-A277-7C086EAD8A4E'.':
It's strange but some days ago I was not asked for the PIN when I deployed the app. :-( So currently the only option I have is deploy via the web portal. This works but it's enormously slow :-(
Can someone tell me how to solve the problem or what PIN should I enter in order to achieve the deployment?
I had this problem today, closing visual studio and restarting IpOverUSB service fixed this issue for me.
You might want to take a look at Ricardo Pieper Question he has listed all the things he tried to do and all the things that might work.
It looks like the problem was caused by the fact that I'm developing inside a virtual machine (VMWare Fusion on Mac). After setting up the development ebvironment on a PC the deployment works fine.
I can even debug the app running on the phone from inside Visual Studio.
Here's a solution which worked for me:
I had the same problem on my Macbook running VMWare Fusion and trying to debug on my Lumia 950 phone. I was nearly giving up, then I tried using the free VirtualBox and with a virtual USB 3.0 port (which requires the VB extension pack). And it worked!!
Here's my setup:
VirtualBox 5.0.14
VB Extension Pack
Win 10 Development VM from Microsoft – the VirtualBox variant, Build 201601: https://dev.windows.com/en-us/downloads/virtual-machines
Lumia 950 with Windows 10 Mobile 10.0.10586.29
In the VM, I configured to use the USB 3.0 port, since with USB 1.x the phone device driver could not be installed by Windows 10.
The VM contains Visual Studio 2015; I created a UWP JavaScript application and ran it with "Debug" on the connected Lumia device.
Had to go to the Developer options on the device.
Switch back to "Windows Store Apps" option, and then back to "Developer Mode"
I'm having issue on Visual Studio Pro 2015 when trying to debug (ARM Solution Platform selected) on a Windows 10 Mobile physical device on my desktop.
The physical device: Nokia Lumia 920 OS Build 10.0.10586.36 (Developer mode) (device not in lock screen and is powered on)
My Desktop: Windows 10 Pro, Intel Core i5-4670K 8GB RAM 64-bit OS Build 10.0.10586.36 (Developer mode)
I do not have this issue on my laptop using the same Nokia Lumia 920.
Severity Code Description Project File Line Suppression State
Error Error : DEP6100 : The following unexpected error occurred during bootstrapping stage 'Connecting to the device '30F105C9-681E-420b-A277-7C086EAD8A4E'.':
DeviceException - Deployment failed because no Windows Phone was detected. Make sure a phone is connected and powered on. App1
Error Error : DEP6200 : Bootstrapping 'Device' failed. Device cannot be found. Deployment failed because no Windows Phone was detected. Make sure a phone is connected and powered on. App1
So far I've tried restarting both devices and re-installing Visual Studio 2015.
EDIT: So after I've tried the proposed solution, this is what I got even for my emulator. Tried re-installing and repairing, nothing works.
Severity Code Description Project File Line Suppression State
Error Error : DEP6100 : The following unexpected error occurred during bootstrapping stage 'Connecting to the device '8BDF218D-FDBB-4A97-90F9-3AA33B559A92'.': DeviceException - The system cannot find the file specified. App1
Error Error : DEP6200 : Bootstrapping 'Mobile Emulator 10.0.10240.0 WVGA 4 inch 512MB' failed. Device cannot be found. The system cannot find the file specified. App1
I was able to solve the emulator issue by Installing a newer version of Microsoft Emulator for Windows 10 mobile from https://dev.windows.com/en-us/downloads/sdk-archive.
Next I'll try deleting the driver from device manager and if that fails, I'll restoring my device to factory defaults, enable developer mode, and try again to deploy on a physical device.
EDIT: As for the device issue, I deleted the drivers from Device Manager and now I'm able to deploy my apps onto the physical device.
Lumia 920 Driver
The solution is your project need to be deployed first, but may be Emulator 10.0.14393 can't work as good as you want. Following below step can help you.
Turn off Hyper-V
Device Manager: Uninstall Hyper-V driver
Restart
Download Emulator (Version 10.0.10586.11): https://go.microsoft.com/fwlink/p/?LinkId=698769
Restart
Deploying project by Emlulator ver 10586
Deploying in higher emulator version or real device.
It was successful with me!
Does the computer detect the device?
I get this same error when developing with my Windows 10 device and VS105, even though my device is detected by my computer. While I haven't been able to find a permanent solution, the following steps work for me:
Shut down Visual Studio
Unplug your device from your computer
Turn Developer mode OFF on your device.
Plug your device back in
Start up visual studio.
Try running Debug again on your device. It should now come up with another error relating to the fact you don't have developer mode turned on.
Turn developer mode back ON on your device.
Debug should now run.
If you unplug your device, you'll need to go through these steps again before VS can detect it.
EDIT: It might also be worth trying the top answer here: How to develop windows 10 uwp on real device (mobile)?
There were errors in VS2013 when a Windows Phone 8.1 App is launching for deploy and debug:
Error 1 Error : DEP6100 : The following unexpected error occurred
during boostrapping stage 'Connecting to the device':
SmartDeviceException - Deployment failed because no Windows Phone was
detected. Make sure a phone is connected and powered on. AppWP
Error 2 Error : DEP6200 : Boostrapping 'Device' failed. Device cannot
be found. Deployment failed because no Windows Phone was detected.
Make sure a phone is connected and powered on. AppWP
After performing of many method trying to eliminate this problem (disabling firewall, reinstalling SDKs, updating Lumia 930 to the latest Windows Phone developer preview), I managed to deploy and run an app with debugging. And as topic says, deploying and debugging is possible only with disabled WiFi on the Phone.
After enabling WiFi on the Lumia 930 device while connection of VS-debugger/PowerTools is established, then the debugging session stays connected and working. But if I disconnect Windows Phone Developer Power Tools (8.1) and try to connect again (while WiFi is enabled), it says:
Power Tools can't communicate with the device. Here's the error message:
0x80131600 - 0x80131500 - 0xC0000374
Visual Studio can deploy and start a new debug session after enabling of WiFi even after restarting of a VS2013.
But, after restarting the Windows Phone IP over USB Transport (IpOverUsbSvc) service, VS2013 becomes unable to deploy and debug again until WiFi is disabled again.
That's how it behaves.
UPDATE: After updating to Lumia Denim, the bug was fixed.
I have solved it with the following steps:
Open Windows Search, search for "services".
Find the Service “Windows IP over USB Transport (IpOverUsbSvc)”.
Alter initialization type for automatic and click mouse right button and select Start.
Try running !
I put this answer on another post but I guess some did not feel it was an appropriate answer because I didn't find the exact cause - Can't deploy window phone apps to Emulator. Error DEP6100 & 6200. I see that you are having a few issues that I did not originally have but overall I was having weird symptoms. Below is what I did to remedy the DEP6100 and DEP 6200 errors.
I'll start by saying that reloading Visual Studio 2013 and Windows Phone SDK 8.0 did not fix my issue. What did correct my issue was creating a blank project within the Visual Studio Express 2012 for Windows Phone and deploying the project. Then I went into Visual Studio 2013 and tried deploying my project again and voila, it worked. Why, I have no idea but my guess is there is a file or configuration that is set up by VS Express 2012 for WP that has been missed in the VS 2013 with built in WP SDK.
I had a similar experience with VS 2013 where I could not connect the debugger to the device AND the app would crash out with WIFI enabled (emulator was fine)
I solved these problems by installing VS2015 Enterprise RC
When I go in to debug the app, it asks me to choose where I would like to deploy it. When I select Windows Mobile 6.5.3 Professional Emulator and click the Deploy button, it starts to work and throws up a command line and then it goes away and Visual Studio doesn't appear to be in debug mode.
I have the Device Emulator open, Windows Mobile 6.5.3 Professional Emulator loaded and cradled. Can someone help me figure out why it will not let me debug this project?
Brad, I downloaded the code and just unpacked the zip to D:\boxoffice_mobile (a local drive partition). Then I started VisualStudio 2008 and opened the solution file. I get a warning message that the project is not loaded from a trusted location (http://msdn.microsoft.com/en-us/library/bs2bkwxc%28v=vs.80%29.aspx). As I do not use a network drive, I ignored the warning two times and the projects load all fine.
BTW: I found a great tool to manage these 'security' warnings: http://blog.codingoutloud.com/2010/03/05/the-project-location-is-not-trusted-dealing-with-the-dreaded-unblock/. The message had nothing to do with a remote file access.
Then I just looked at the solution configuration to ensure that only the needed projects are build and did no change, as only BoxOfficeMobile and WebserviceTest are set to build and only BoxOfficeMobile is set to deploy.
Then closed solution configuration manager and just pressed F5 to start debugging to see what happens.
The startup project BoxOfficeMobile was build and deployed to "Windows Mobile 6.5.3 Professional Emulator". The emulator started and the files were deployed and the project was stopped by a breakpoint inside the code:
Here is another screen shot with the emulator set to 'Display: Always on top':
So, as you can see, the project is fine and the debug issue on your site is caused by a different setup.
Do you load the project from a network drive share? Try moving it to a local drive and run it from there.
Did you change Device settings in the VS2008 Tools:Options menu? Here is my setup (as coming as default, I did not change anything):
and the details:
The additional settings available via the buttons are empty (Configure) or unchanged (Emulator Options).
I am very interested in seeing what you changed to be not able to debug the project.
before you start developing for Windows Mobile 6.5 Prof, you need to setup your development environment.
First, install Visual Studio 2008 (no express version)
Download and install either ActiveSync (host OS <= Windows XP) or Windows Mobile Device Center / WMDC (Windows Vista/7)
[optional] Download and install Device Emulator Manager
Then download and install Windows Mobile 6.5 DTK (http://www.microsoft.com/en-us/download/details.aspx?id=5389)
Now, you can start a new C# project inside Visual Studio 2008:
Follow the wizard:
The list of Target Platforms depend on the Mobile/CE SDKs you have installed!
Select either .Net Compact Framework 2.0 or 3.5. The choose depends on what is installed on your PC and what is available on the device. If the device comes with 2.0 pre-installed, I would choose 2.0 except for I need something only available in 3.5 (ie Mobile.Status namespace).
Now you get an empty form:
You can change the target device in the project properties:
If you want to change the target platform, look at "Change Target Platform" in Project menu or just right click the project in solution explorer and select Change Target Platform:
The above has nothing to do with Device Emulator Manager or the installed Emulator Images!
You can run a WM5 targeting project on a Windows Mobile 6.5 device if you want.
To start debugging and SmartDevice application inside an emulator. Just Select an Emulator entry from the target device list in Project properties or just in the SmartDevice toolbar. Then click Debug and "Start Debugging". VS will start an emulator with the specified emulator image and deploys your project application files and start remote devugging.
You may also start an emulator image using DeviceEmulatorManager and then cradle the running Emulator image. To use the running and cradled (ActiveSync or WMDC connected!) emulator do NOT select an emulator inside VS but a Device. VS does not see the difference and uses the WMDC connected device, regardless of being an emulator or real device.
VS uses DMA to communicate with the emulator, not USB or Serial as with a real device.
Now start your development.
First of all clean your project.Then freshly start the emulator.Right click the project and select build.Then Debug the project.Your project will be started in Emulator (Don't Open the application from your Emulator at this time).
Just check your Emulator Start>File Explorer>My Device>Program Files whether the project has been previously installed.If so uninstall from the Settings> System > Remove Programs. And try re-building application and deploy it.