2 ms·
The differences in experiences are huge. I use VS occasionally and basically expect something to be broken every time. Maybe I'll open a project and the error l
by viraptor 3y ago
The differences in experiences are huge. I use VS occasionally and basically expect something to be broken every time. Maybe I'll open a project and the error list will be full of "type Object unknown / type String unknown". Maybe the editor will be empty. Maybe the publishing will claim the existing artefact is newer than what I'm building. Maybe autocomplete won't work. That's literally my list from just this week.
A restart of VS usually fixes the most recent issue or replaces it with a different one. That's been my life for the last 3 years.
- gambiting 3y agoI think I've heard complaints from people using it more with .net workflows, I'm a C++ programmer myself and it's been as solid as anything.
- samsaga2 3y agoVisual Studio C++ programmer here. My Visual Studio crashes depends a lot on the last update. Some updates work correctly, another ones have a lot of crashes. Now I have like three or four crashes per day with the last one (no problem with the previous one).
- jahnu 3y agoAlso c++ dev and I use Xcode also on a daily basis. VS is the best IDE for me and I have tried them all. Solid, excellent debugging tools. I think it helps that I generate my solutions from CMake so they are always “fresh” and not really old ones that have been upgraded multiple times, which I suspect is the cause of many issues in VS. I also did a fair bit of .net in my last job and I could not live without Resharper C#. If the company wouldn’t have paid for it then I would. Resharper C++ is not good though.
- pjmlp 3y agoAs someone that uses it for both workloads, it does just fine, don't load it with lots of plugins. If anything, plugins creating havoc on host processes have given a reason why extensibility should be done out of process with IPC, despite consuming more resources. Not only on VS, on other IDEs as well. Given that, it is no surprise that the new extensibility API is out-of-process.