Blazor WASM Standalone Debug stopped working - visual-studio-code

I've been developing blazor wasm apps in vscode for the past few months without incident. All of a sudden, I can't debug via F5 any longer. I'm literally starting with a brand new app (dotnet new blazorwasm) and when I hit F5 I get the following error:
I've uninstalled/reinstalled vscode, chrome, updated .net core 5, tried Edge put things into my launch and launchsettings.json that have helped others and plenty of other things things that I can't recall. Even created a new account on my computer to eliminate possible plugins or settings, same problem.
One thing that does work is that I can debug the old way where I would run Chrome from the command line: open /Applications/Google\ Chrome.app --args --remote-debugging-port=9222
Then you can hit Cmd+Shift+D in Chrome to start debugging within Chrome. This is a stop gap, but I'd really like to figure out how/why this just stopped working.
I created repo that reproduces it on my machine.
I'm not finding a lot of ways to gather diagnostic details that might help me determine the cause, so would appreciate any tips that would help me solve this.
Using latest chrome and vscode, even tried the insider build. No luck. I'm not sure what I did or how to fix it. Any help is greatly appreciated!


This is todo with omnisharp update. I get the same. You can downgrade omnisharp as a test and it will work again. I am investigating.

Related

VSCode Marketplace Does Not Load

I have recently downloaded VSCode, but my most basic functions were not working due to "cannot edit in read-only editor" error. Thank to stack overflow I fixed the issue by changing code runner settings and enabling editing through the terminal. Then I tried to move the program from downloads folder to applications, when suddenly the extensions marketplace stopped loading. When I go to "Help" --> "Toggle Developers Tools" --> "Console", I see two messages:
I am using MacBook Pro (2020) and have no idea what to do. I am very new to programming and would really appreciate any help.

I'm not sure if this is gonna help, but you can reinstall VSCode again, this time put the app in the Applications folder. If the marketplace doesn't load maybe it cannot connect to the DNS, try to change the DNS address to google's 8.8.8.8.
Also, take a look at this, it seems similar to your issue. https://github.com/Microsoft/vscode/issues/54033

How can I investigate extensions problems with Visual Studio for Code?

When I click the Extensions I get nothing on one of my computers. I have checked the marketplace is not down. I have tried to delete the app and download a new version. Nothing helps. So are there any ways I can investigate this further? Quite frustrating to not been able to install extensions...
I'm on a Mac with Catalina 10.14.6 and I have VS for Code 1.41.1. I launched the Console app and see some messages from Electron(which I suspect is some part of VS for Code since it is mentioned in the about window) but none really makes sense.

Unity Hololens project missing SDK (that is certainly installed)

I made a stackoveflow account just to post about this since it's been bothering me for 3 days time (tinkering after work so not much time every day). And this is my first post so please be forgiving if I break a few rules :)
My problem is that after I have installed and configured everything and I have followed the official guide I get these errors thrown by VS
I have researched as much as I can and still nothing. Things I have tried:
Reinstalling VS
Reinsatlling and manually installing the Windows 10 SDK
Adding all the sdk folders to the Path Env. Variable
Rebuilding the project
Building a new project
Changing the version of the UWP
Has anyone else had this issue or know a way to fix it? I really want to start developing for MR after doing a ~10 page documentation on why its the most promising technology...

Error : DEP6200 : Bootstrapping 'Device' failed. Device cannot be found

I've read every StackOverflow that I could find on this issue, but I still can't work it out.
I'm trying to deploy an app to actual device (NOT emulator). But I receive the following error when i try to build:
Severity Code Description Project File Line
Error Error : DEP6100 : The following unexpected error occurred during bootstrapping stage 'Connecting to the device '30F105C9-681E-420b-A277-7C086EAD8A4E'.':
SEHException - External component has thrown an exception. App1
and
Severity Code Description Project File Line
Error Error : DEP6200 : Bootstrapping 'Device' failed. Device cannot be found. App1
It's worth mentioning that I went from Windows 7 to Windows 10. It's also worth mentioning that my computer was missing the IpOverUsbSvc.exe (not just the registry post, but the actual service was missing). Couldn't find any way to get this back so, so my colleague sent over the .exe and the DLLs and I placed it in it's location. And the service is now running and no longer gives any errors. My device is recognized by the PC, it's running Windows 10 Mobile (but I've also tried with a device running Windows 8.1).
Specs on PC:
Windows 10 Pro (Build 10240)
Using Visual Studio 2015
UWP Tools
Any suggestions to fix my nightmare? Thanks!

Steps that helped me. I have windows 10 mobile build 10581 (and now 10586) installed on phone
Turn off Developer mode on your phone.
Deploy app (UWP or SL) by VS2015 -> Error.
Turn on Developer mode on your phone.
Deploy app (UWP or SL) by VS2015 -> Working.
If you change another device or re-connect you must close VS2015, re-launch and do again!

Finally managed to find a solution to this illusive bug.
It seems that if I didn't have the Windows Phone 8.1 Tools installed I couldn't build to an ARM device (not even Windows 10 Mobile).
So my step to solve this was:
Go to Control Panel -> Programs and Features -> Microsoft Visual Studio ... 2015 -> Modify. And then select the Windows Phone 8.1 Tools.
Pretty pissed that one can't get a reasonable error message when things like this is missing.

I had this issue after updating my device to win10 ver:10.0.10581.0. I tried many things but finally after installing latest sdk and emulators i got it working. You may try installing from this page sdk and emulator:
https://dev.windows.com/en-us/downloads/windows-10-developer-preview
Somehow the new emulators were not visible in vs, they got visible after few restarts and then on device debugging started to work.
But one problem still remain from me that vs crashes after ending debug session with device.

desktop-->my computer--> right click--> management--> service--> start the service Windows Phone IP over USB Transport (IpOverUsbSvc) although maybe the starttype is set as automatic

Seems like there are many issues causing the same error message.
This one worked for me Windows Phone deploy Issue
Essentially you need to remove/uninstall the device from Windows. Then after unplugging and plugging back in, the device and drivers are reinstalled.

I tried many of the suggested solutions to no avail.
After changing the USB-C cable from a USB 3.1 port to a USB 2.0 port on my computer, the error goes away. YMMV

I see it is quite an old post...but I still get this problem. In my case, this happened after I deployed to a second phone I had for testing. After that, VS 2017 now only wants to deploy to that phone and not to the other phone no more. If I start another project, the other phone is recognized and deployable to (listed as device under debug).
Restarting system fixes this...
Also, if I add another project as reference (like a background task) to my project, I will loose the ability to select the devices and emulators under debug. VS 2017 simply then seems to deploy to the last device selected...(really no clue what this is). I have not been able to get the selection of emulators and devices back yet on this one. I only will have the "Start" and "Download new emulators" options. I think this has to do with the fact that VS maybe doesn't know the type (like arm/86/64) of the reference project because it is not set (not needed as this defies the purpose of referencing a project for dynamic references and not the compiled device specific file...)
Hope it helps someone ....

I uninstalled the existing version of the app in device and re-ran it and it worked for me

I got that error for a really simple reason...just opened a new solution I downloaded from GitHub, pressed F5, and got it!
I had left my build configuration in the default "Debug - ARM" setting, when I changed to "Debug - x64" it worked fine!
(Just adding another reason for completeness, not likely to affect your case!)

In case it's helpful for others... I got: DEP6701 bootstrapping failed ... access denied.
Thanks to comments here, I only dev-locked then dev-unlocked my phone (was originally dev-unlocked). Totally works now (took some time installing missing frameworks at first). All good.
Thanks

One more thing could be tried.
Uninstall the existing app if any and then deploy from Visual Studio.

Try on another usb port. It worked

Eclipse using Android emulator

I wonder if anyone has faced the same problem.
When we done some modification on the code, as the emulator is running; is there any way we could see the instant change without closing the emulator?
Sometimes when I made changes on the code then run the emulator, the amendment that I made doesn't seem to show on the emulator even after I clean the project.
Does anyone have any idea how to solve this?
Thanks.

Eclipse has an option under 'Run' in the menu bar to build, and run. This will re-package the application and send it to either your AVD, or attached android phone.