3 ms·
For c# visual studio .NET in 2012 (I really haven't used it since) with its refactoring tools was pretty quick and its compilation system with integrated error
by bhouston 8y ago
For c# visual studio .NET in 2012 (I really haven't used it since) with its refactoring tools was pretty quick and its compilation system with integrated error checking in the text editor. It was really productive.
When I switched over to JavaScript I miss that a lot. Of course JavaScript just doesn't lean itself that well to automatic refactoring and the build process is significantly more complex too, so you only get local syntax checking usually in the editor.
And then eventually VS.NET got auto-help where it would should you documentation in a side window if you typed in a function or hovered over one. That was nice when using APIs you were not familiar with.
You could actually find all references/usages and be sure it was actually correct. I could click on an include and it would actually open the file no matter what and if it was referencing a DLL/Assembly it would immediate give me a decompile/documentation link.
The downside of the visual studio approach was the lack of text-based configuration. I spend hours adjusting settings in project files. (This was addressed via CMake when dealing with C++ but I do not think there was an equivalent for C# that I was aware of that the time.)