1. Introduction
2. Code Editor & Designer
3. Debugging & Tools
4. Conclusion

Comments

1. Krzysztof Witukiewicz
   19 Oct 2006 at 09:43

   I use VS 2005 Team Edition in a big projekt. I find this IDE a step backward. Refactoring functions are painful (i.e. why, when I want to rename local variable in a function, it tries to rename all ocurrences in whole solution?) To add functions known from Eclipse (i.e. error highliting while coding - this is most useful to me, advanced finding usages, i.e. going direct to inheritors, super-fast finding of classes with a list of possible options while typing), you have to install separete Plugin. This is such a pity, while this consumes much memory. With big project, such as our, overall tool performance is bad. In my team are colleagues, which in other projects worked with Java and Eclipse. Their opinion is, that Eclipse is much better. Not to insult anybody. We use it for developing client-server application, where client is desktop (winforms) application. I've heard, that VS is very helpful when working with ASP. My company has no big experience with this technology, we used mainly Java so far.

2. James Crowley
   02 Feb 2004 at 12:44

   However, at that page says
   

   
   "Visual Studio .NET does not support Edit and Continue for Visual Basic or Visual C# code."
   

3. Joe Wilson
   02 Feb 2004 at 11:40

   You can debug while your editing..
   

   
   You have to change your options,
   

   
   here's how to
   

   
   http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsdebug/html/vxurfeditcontinuedebuggingoptionsdialogbox.asp
   

   
   PS It's called Edit and Continue

4. smithalpha
   27 Oct 2003 at 06:57

   I'm relatively new to .NET, I have programmed in VB 6 on and off for a few years and I find the main annoyance for me is the inability to enter code while debugging, you can't even comment out lines. I'm not even sure if you can skip over lines of code while debugging. I'm finding it very frustrating. Does anybody know of any work arounds. Another gripe is do people notice how difficult it is to find even the most basic information on Microsoft and other products online these days.
   

5. Aaron Hudson
   29 Apr 2003 at 14:42
   Brilliant article and is totally correct in what is said.
   
   I began programming a year ago with Visual Basic 6, after becoming very much used to the VB6 interface, using VB.NET is a huge shock to the rituals. Visual Basic is like a totally new language. For example, something as simple as changing a Form's Back ground colour is now: Form1.BackColor = System.Drawing.Color.Red which is a lot more complex than what it is.
   
   VB.NET is as good as a new language, but will give new programmers a boost in learning other languages, such as the hyped C#.
   
   Personally, I still prefer VB6, but along with all the changes, VB.NET is a lot more powerfull. I've got both VS6 and VS.NET installed, so I can get the best of both worlds, although I think I will be a complete .NET programmer within the next few months.
6. Developer Fusion Bot
   01 Jan 1999 at 00:00

   This thread is for discussions of Visual Studio .NET Professional.