I’ve been using Visual Studio for almost 20 years as my primary code editor /project manager and for all that time it’s been solid. If there were errors it told you and highlighted/underlined them before you tried to build no matter where the error was in the entire solution.
I am willing to accept a slight decrease that solidness in order to gain the extra flexibility provided by dotnet core over framework. However…
My experience with the recent updates to Visual Studio have culminated into a state where errors that exists are not detected, or if they are (ex. on rebuild) they are only reported, not underlined. Once I find and fix the error it remains in the list until I rebuild, if there are other errors it will remain until I find and fix each of them (which themselves will remain in the error list…) and finally rebuild.
I’ve adjusted options, to no avail. Sometimes restarting VS helps for a few minutes sometimes deleting the .vs folder will help for a few more…I feel like It used to be a lot nicer.
Today I’m seriously considering moving to a plain code editor and using the donet cli for build/test/publish.
Is anyone else experiencing problems like this?
You must log in or register to comment.
Gods yes. I’ve had so many errors spontaneously come into existence these past few months, that are resolved by rebooting the computer. I’m guessing it’s some language server fuckery.
One of the biggest annoyances for me is that it’ll spontaneously decide that WASM tools isn’t installed. I was working on this project about two hours ago and everything worked fine, decided to go for a walk with my dog, and when I came back suddenly the project no longer builds because WASM tools has ceased to exist. I found this thread while scrolling through Lemmy waiting for the umpteenth reinstall of WASM tools.
Some days I’m thinking about just… throwing my computer out the window and moving to convent or something. I hate tech.
