Visual Studio code was working fine with maven projects, and suddenly stopped after I installed a new extension (Lombok).
I can't seem to get it to work anymore, even if I'm not using Lombok, and have the plugin disabled.
As soon as I start Visual Studio Code, it complains with
Couldn't start client language support for java
How can I fix this?
To solve this, I did the following:
Went to the installed extension (Command Pallette, Extensions: Installed Extensions)
found "Language suppoort for Java(TM) by Red Hat"
Clicked on the drop down arrow by "Uninstall", and chose "Install another version"
Chose a recent version, and restarted Visual Studio Code
it worked - I assume I could upgrade to latest again, but haven't done so yet.
Note: I feel that somehow I broke my settings.json file, and doing this fixed it up.
I am developing Unity game apps on a PC using C#, using Visual Studio Code as the editor. The apps are targeted at PC and Android. Multiplayer uses Photon Pun 2.
The Unity version is 2019.3.14F1 - I don't want to move forward just yet in case of 'unexpected problems'.
The VS Code version was 1.48.3 - and everything was fine, no compile errors, all code working OK etc.
Stupidly, I took Microsoft's advice to update VSC, and VS Code went to 1.50.1. Result of this is that there are all sorts of errors showing up in VS Code relating to the Photon code. All these errors stem back to the 'using Photon.Pun;' line. It says "the type or namespace name 'Pun' does not exist in the namespace 'Photon' (are you missing an assembly reference?)".
The code however does not come up with any compile errors in the Unity editor itself, and it all runs fine, including the Photon parts. The problem is in VS Code.
I realise this is almost certainly as VS Code problem, not Photon, but I am wondering if anyone has met this before and knows how to fix it?
(This is why I do not want to move from 2019.3.14F1 to 2020.whatever at the moment - you never know what might happen).
I had the same problem. Installing different versions of VS Code / VS Community Edition didn't fix anything for me, but this did:
With the project open in VS Code, find all occurrences of
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
in *.csproj files, and replace them with
<ReferenceOutputAssembly>true</ReferenceOutputAssembly>
Tried rebuilding project files, swapping to a different editor (VS Community Edition 2019 - that was fine), but no difference - VSC persisted with the errors. Rest of intellisense working OK.
In the end, totally uninstalled VSC and reinstalled, and that sorted it out. No idea what the actual fault was.
I was wrong.
To-day, the errors are back.
The reason appears to be that in the process of trying to sort this, I installed VS Community Edition 2019 to see if that worked OK (it did). Then went back to VSC, and - that was fine too. Later I uninstalled VS Community Edition 2019 (it is taking about 4GB). It was uninstalling that which brought the errors back into VSC. Reinstalled VS Community Edition 2019, and it is all fine again.
So, VS Community Edition 2019 installs something that VSC needs - but I haven't yet figured out what it is.
UPDATE:
Gave up. Never managed to find out what VSC wanted and wasn't getting. Instead, reinstalled old version of VSC (1.48.2 from code.visualstudio.com/updates) and it is all fine again.
If still having this problem, all you have to do to fix it is by going to Package manager and install "visual studio editor package"
windows>Package Manager> All Packages /or Unity Registry (depeding on your unity version) search of visual studio editor
if it's already installed delete it and reinstall.
Got it FIXED!
Solution (it was a Unity issue):
In Unity, goto Edit > Preferences > External Tools > External Script Editor, and point it to Visual Studio..
Why this was so hard to find, I have no idea. But now my Photon solutions and namespaces properly transfer from Unity to Visual Studio. Hooah!
Also moved the script to where the photon scripts are
Uninstall the Visual studio community and re-install with latest VSC 2022. It will fix the issue
I've recently uninstalled VS 2015 and some other packages which I don't recall. Ever since the uninstallation I've not been able to view the the icon of VS Code, VS Code Insider and Windows Defender. All those software were working properly previously.
[
If I click on those application, they won't open.
But if I selected a file or folder and open them by selecting the option "Open with VS Code or VS Code Insiders", there is no any problem. The icon of those software can't be seen on the taskbar too even if they are opened.
What package should I need to install again to make them appear? What other software might be affected?
I have a project using the SpeechClient.dll from NuGet. The program runs fine on the development machine. So I have a Windows Setup Project that creates the installer. I run the installer and all the files show up including the SpeechClient.dll, but as soon as the program makes the first call to the Speechclient.dll, I get a
file not found
exception. This is the output from the event viewer.
Does anyone have any troubleshooting ideas? Thanks.
Seems now that I have installed visual studio on the machine that it is working. I wonder what visual studio installs? I was also trying to use Fusion Log Viewer to see what the problem was.
I had this problem as well. Installing the Visual Studio C++ Redistributable 2017 x64 cleared it up.
Almost every time I try to rebuild a C++ project in Visual Studio 2010 after having recently launched the build target from Visual Studio, I get this error.
LINK : fatal error LNK1104: cannot open file 'D:\Programming\Projects\SpecsLauncher\Release\SpecsLauncher.exe'
I have used ProcExp from Sysinternals to check and see which application still has the file open, but it comes up with the System process as still having it open.
It does not appear anywhere in the Windows Task Manager, and closing and re-opening Visual Studio makes no difference.
I can't even delete the build target from Windows Explorer.
I do not experience this issue with anything other than executables built and run from Visual Studio.
I thought it might be my anti-virus (Symantec Endpoint Protection), so I tried temporarily disabling it, but it made no difference.
The only thing I can do is wait about 4 minutes and then try again.