"In fact i have been an "texteditor-only" type in the past, but coding C# in Visual Studio has really been a revelation for me."
The fact that application X is "just a text editor" is not a justification for X having poor editing functions. In fact, you'd expect a specialized text editor to have better editing functions that an IDE, since an IDE can have other selling points, such as an integrated build system, a version manager, a profiler or a debugger, whereas an editor can only impress you solely by its usability for...well, editing.
Yep you are right, i meant this more in a way of working style.
In the past i thought its the best approach to only use a text editor and do everything by hand, know your Code, work like a pro etc. But just simple things in VS like "Jump to Definition" or "Find Usages" combined with powerful IntelliSense and Refactoring functions is such a joy to use.
I didnt even talk about the debugging tools, but well i am an IDE guy now, at least for large projects.
The fact that application X is "just a text editor" is not a justification for X having poor editing functions. In fact, you'd expect a specialized text editor to have better editing functions that an IDE, since an IDE can have other selling points, such as an integrated build system, a version manager, a profiler or a debugger, whereas an editor can only impress you solely by its usability for...well, editing.