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.
Related
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.
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
Nothing was changed when all of a sudden Visual Studio 2019 suddenly couldn't open Unity 2019.2.4f1 projects.
Once it happened several months ago. That time it was cured by itself when I downloaded a clean Unity project from my repository. Just yesterday it happened again. I spend the whole day surfing forums and trying to fix but nothing helped until I decided to completely reinstall Visual Studio. Today everything was fine until suddenly it started again.
I didn't change anything, just was working with code.
External tools settings are set as they were.
Any ideas why it could happen and how to fix it without reinstalling VS?
Is it possible to somehow find out what exactly the VS can't understand in the project files?
In VS2019 go to Extensions -> Manage Extensions and check that "Visual Studio 2019 Tools for Unity" extension is installed, and enabled.
I just downloaded a fresh copy of VSCode-darwin.zip from https://code.visualstudio.com/, upzipped, dragged to my Applications directory, and tried to run it. After the initial "Verifying Visual Studio App" window ran, the dock icon bounced a few times then vanished and the app didn't load. Subsequent attempts yielded the same result. Anyone else experience this? Any known conflicts or dependencies for 10.8.5?
VS Code does not support Mac OS X 10.8 and below. We have a dependency to Electron and updated recently which caused this.
I thank you all for reading this lengthy question. It's really important and I will appreciate it if you can assist me :)
The problem -------
I am have been using the Windows 7.1 SDK for about two months now. The emulator has worked without any problem so far. However, today, it began displaying this error (The saved state (Name of File).dess is corrupt. Please delete the corrupted saved state file and then retry). I had not made any significant changes to my project code, or moved any files. I had just added some Visual State animations for a button.
As it suggested, I went ahead to delete the file. I then started debugging again. However, the emulator now opened and displayed the message (Windows Phone Emulator is doing a complete OS reboot). This message was displayed for a very long time. I closed the emulator and project. Since then, I have been unable to use the emulator. I am able to code normally in Visual Studio, but I cannot test my application.
What I have tried ------
I read up on this issue and found many others who faced the same emulator issue. Following their suggestions, I have run one repair of the Windows Phone SDK 7.1. I have also tried uninstalling and then re-installing the SDK 7.1 once.
System Specifications -----
I am using Visual Studio Express 2010 for Windows Phone (Windows 7 64 bit)
I have downloaded the Windows Phone SDK 7.1 from this link: http://go.microsoft.com/fwlink/?LinkId=258412
I have read that this issue might be because of some hardware incompatibility. However, I think my machine is compatible with the emulator. Here is some information.
DirectX Version: DirectX 11
8GB RAM
Driver Model: WDM 1.1
Additional Information:
I have read that installing the 'January Update' might fix this issue. I tried downloading the update from this link: http://www.microsoft.com/enus/download/details.aspx?id=23854
However, the installer said that the update is not compatible with the product/version of the product I am using.
Usually the Repair function of the WP7.1 SDK is enough to fix all the issues. It runs the generation of the saved state of the emulator again.
Please try to delete files in %ProgramData%\Microsoft\XDE folder first (make sure you backup them somewhere else.), then run the emulator. If the emulator runs with a message "Windows Phone Emulator is doing a complete OS boot," let it boot. It takes some time though. This way you will know that the emulator actually can run on your computer. This won't generate a new saved state image, but the emulator should at least load.
Next, try installing WP7.1.1 SDK update from http://www.microsoft.com/en-us/download/details.aspx?id=29233. This update also installs additional 256MB emulator image besides the original 512MB image. It also generates emulator's saved states in the process, potentially fixing the issue.
If everything fails, then try these instructions to fix the saved state of the emulator:
Uninstall WP7.1 SDK
Manually delete these folders:
%ProgramData%\Microsoft\XDE
%LocalAppData%\Microsoft\XDE
Install WP7.1 SDK again.
Install WP7.1.1 SDK update: http://www.microsoft.com/en-us/download/details.aspx?id=29233.
Edit:
Btw, have you tried to reboot your computer? Once this fixed the issue for me.
Alright, I managed to solve this problem.
I reinstalled Windows and downloaded the SDK 7.1 again. The emulator works fine now!
#Paulos, thanks for helping!
I had the same problem for a long time. Try this:
Start up Visual Studio 2010, but before you start debugging, click on the tabs of all the open pages so that all the xaml pages and code behind pages can load.
I noticed it when I opened Visual Studio, but the first open page was a code behind page and not an xaml page, so when I first clicked on the tab of a xaml page, of course, it took some time to load the xaml page into the editor. However, when that and one or more open xaml pages were also loaded, the emulator started without the error message.