I have seen few posts here about same error but none worked for me.
I am trying to deploy UWP from VS2017 from one machine to a Surface machine that is USB connected to the machine running VS2017.
Both machines are running Windows 10 Pro, 17134 (1803) April Update.
Surface machine has enabled Developer Mode in "For Developers" settings and Developer Mode package is installed on it and Remote tooling for desktop is enabled. It is also USB connected to the machine running VS2017 Enterprise 15.7.5
According to MS documentation, that is all what is needed to deploy to device. However, deploy fails with error
Severity Code Description Project File Line Suppression State
Error DEP6200: Bootstrapping failed. Device cannot be found. SmartDeviceException - Deployment failed because no device was detected. Make sure a device is connected and powered on. [0x80131500] MyApp.App.UWP
I was unable to deploy either to device or to use remote debugging.
Deploying to device was failing with the same error message as above. Interestingly, even if device (Surface in this case) is not USB connected to my dev machine at all, I get same error which basically makes sense. But I dont know why I get that same error when I connect Surface tablet to my dev machine.
Deploying for remote debugging did not work since my Surface tablet is not connected to same LAN as my dev machine.
So, for my testing purposes, I deployed by using USB stick
Right click on UWP project, choose Store, then choose Create App
Packages ....
In Create App Packages window, select "I want to create packages for
sideloading"
Click Create
Leave Local Machine as target device for validation
click on Launch Windows App Certification Kit button to launch it
and go through steps until complete
Once package is completed, I copied entire folder onto a flash drive
and moved the content of the folder to my Surface tablet
Then on Surface tablet, right click on the Add-AppDevPackage.ps1
file and choose Run This PowerShell
this will start deployment and deploy the app
Related
I installed code-server on a Pixelbook Go (x86 Intel i3 with 8GB RAM, 64 GB SSD). I installed it as a user, not a root, not sure if that's a problem or not. The code-server service is enabled and starts when I start the Developer Linux VM (penguin). As far as I know I'm upgraded to the latest Crostini (104.0.5112.83) and the VM is a Bullseye Debian, I installed it not so long ago.
Outside of the VM I started the Chrome browser and I can view the GUI portion of the code-server by visiting http://localhost:8080 (as per .config/code-server/config.yaml). I installed the Flutter and the Dart extensions in the GUI. I also opened the root folder of my Flutter project (which is a regular project (https://github.com/TrackMyIndoorWorkout/TrackMyIndoorWorkout): no embedded or multi-module things in it).
I connected my phone (OnePlus Nord, Android 12), it displayed the bottom sheet related to the connection and I allowed Transfer. The Crostini detected this connection and popped up a notification about it. I could use that notification bubble to shuttle to the connected USB devices settings and enabled the Nord device.
Here is where things started to differ from starting the "regular" VS Code (installed into the penguin VM from a package) itself: VS Code shows a device selection in the footer section, which lists target devices such as the Pixelbook Go and also the Nord (AC2003) - see screenshot later. However the GUI of the code-server doesn't have selector for the devices. When I start to initiate a debug session it displays an error message:
Unable to launch Flutter project in a Dart-only workspace. Please open a folder close to your Flutter project root or increase the value of the "dart.projectSearchDepth" setting.
Here is how it should look like in the "regular" VS Code:
I opened the root folder of the Flutter project just as I did when I use the "regular" VS Code, so this project search depth doesn't make any sense to me, the dart files are there including the main.dart in the lib folder. And the VS Code kinda works, except that the build hangs due to possibly low resources, hence I'm trying to get code-server working so I can migrate at least the VS Code GUI portion out of the anemic VM. I suspect that the main problem might not be the Flutter / Dart settings, but first I have to figure out whey the GUI doesn't show a device selector. Then I can lament on this error message if still persists.
How to proceed?
I've been working in a Unity app with Hololens emulator in Visual Studio 2017 in Windows Pro, and it was working great until last night where I started to get the following issue every time that I try to deploy my application into the Hololens emulator:
Error DEP6957 : Failed to connect to device '[device_ip]' using Universal Authentication. Please verify the correct remote authentication mode is specified in the project debug settings.
I've tried to do the following things without success:
Clean/rebuild solution
Checked 'uninstall/install' checkbox in the UWP project settings
Deleted Hololens virtual machine
Uncheck/check Hyper-v feature (and restart PC after each try)
Restarted computer
No luck. Sometimes, I am able to make it work, but after 30 seconds to 1 minute, the hololens emulator gets frozen and then it closes itself; again, this was working fine until last night, and I have not installed anything different, unless an automatic windows update did something. This happens with all the applications, and they run just fine in the Unity player.
I would appreciate your help on this, I just don't think the only solution is to uninstall/install Visual studio and all its components, it makes no sense, since everything was ok.
Thank you.
UPDATE
I've just noticed that if I connect the laptop to the internet by using an ethernet cable, it works, it only fails in WIFI, have you seen that before? I also have another UWP that I deploy remotely to a raspberry and it also works only with ethernet, but both of them were used to work in wifi? any idea?
My setup
HoloLens
Windows 10 October 2018 Update (10.0.17763.134)
Desktop
Windows 10 Enterprise
Visual Studio Community 2017 Version
Unity 2018.2.19f1 (Latest 7th December 2018 Update)
The Problem
I am unable to deploy any application to the HoloLens, but able to deploy it on hololens-emulator. I'm attempting with the Origami application exported from Unity as in the tutorial. I'm able to pair with the HoloLens easily and I have developer mode on. Visual Studio also does auto-detect the device as a remote machine. But when I attempt to deploy it, I always get the same "DEP0100" error, that the device is not in developer mode though the device is already in a developer mode. I'm at a loss for what else to try, or what setting I've missed. I've reset the HoloLens several times and reinstalled Visual Studio only to get the same thing.
I have already tried the solution mentioned here Unable to deploy HoloLens application but it didn't work for me.
It is not clear what you got. But I have couple ideas:
You connected to HL as Remote Machine, but HL is Device.
You built an appx as x64, but HL is x86.
You didn't install a proper runtime, debug or release.
You use older SDK than HL platform version.
You minimal target platform is higher then HL platform version.
Maybe something else. You need to investigate the Hololens logs. Open "Windows Device Portal"/System/Logging.
Then you need to select some providers with severity by choosing them in box and clicking "Enable". I usually begin from "Microsoft-Windows-WinRT-Error" ETW provider.
DO NOT CLOSE THE LOGGING PAGE!!!!!
Start the debugger with app, see the error and go to Logging page. Try to find out the root of issue.
In Visual Studio you can go to properties->debugger, select remote debugging and enter the device's ip and port (with the remote debugging tools running on the remote device), hit deploy and press F5 (or ctrl+F5).
I would like to mimic that from a command line prompt or powershell. is there any way of doing that?
I saw lots of posts that suggest creating a package, signing it with a certificate, sideloading the app and running it on the remote device, but I would like to do that from the "master computer" without doing anything on the remote device. Has anyone found a way to do that? If not, how is automatic testing done on such apps?
I tried to run the directx samples from ..\Windows Mobile 6 SDK\Samples\PocketPC\CPP\win32\directx\d3dm\tutorials on a Samsung Omnia and on the emulator and it doesn't work because of a deployment error.
I am using Microsoft Visual Studio 2008 and have installed Windows Mobile SDK Standard and Professional refresh.
The device is correctly plugged in and set up for active sync (I know this because other samples work, also a creating Win32 smart device application and running it works).
When I try to run a directx sample application it compiles without errors but the message:
" There were deployment errors, Continue? Yes/No" appears
If I manually copy the application from the debug folder to the device and run it from there, it works.
The same deployment error message appears if I try it on an emulator. Other applications are deploying successfully.
Is there any way to make the deployment work? Maybe there is an obscure option I need to set...
What I do is:
Connect the Mobile device to the PC,
Open Visual Studio 2008,
Open a directx sample project,
Click Run (in Debug or Release mode).
The problem with the deployment is that the file msvcr80.dll could not be found.
It was specified at the deployment options as an additional file "Project->Properties->Configuration Properties->Deployment" then "General->Additional files"
with the paths msvcr80.dll|$(BINDIR)\$(INSTRUCTIONSET)\|%CSIDL_WINDOWS%|0;
Removing it makes the deployment successful. I have only tested this on a Windows Mobile 6.1 device and with the D3DM reference driver on an WM6.1/WM6 emulator.
What I haven't figured out is where does $(BINDIR)\$(INSTRUCTIONSET) point to.
Also I don't know why msvcr80.dll is in the addition files if it is not actually needed.
Is there actually a msvcr80.dll compiled for Windows Mobile platform on an ARM cpu?
I was able to resolve this issue after doing some low-level Sysinternals Debugging. It was trying to deploy NETCFv35.Messages.EN.cab to the device and in my case it was deleted for some reason. Re-installing .NET CF fixed the issue for me. Wish VS 2008 said what file was missing instead of a generic message. Hope this helps you too.