«« Customer Testing Win2k3 iTunes4 »»
blog header image
Back into VS.NET/C#

After a few days of VS.NET and C# programming I remember what I liked and didn't like about it.

Number one on the hitlist is refactoring support. If I change a button's name in the (user interface) Design view, I shouldn't have to change it's name in the code anywhere -- it should be done for me. It's an incredible PITA to have to do this yourself (to find them I just recompile and fix the errors, but this isn't such a great way to do it). I'm used to the great refactoring support in Eclipse.

The integrated UI construction is decent, but far from perfect. You design a UI and it can resize in completely unpredictable ways. Some of the UI adjustments need to be made in code but at least they can be made. I'd rather have UI construction like XUL. Very clean and simple XML and layout model with a high amount of control. And things don't mysteriously disappear when you resize the window to a small size.

No integrated CVS support that I saw. Again, Eclipse has this and it's excellent.

The XML classes that I've used so far have been great and very well abstracted.

Of course I'm going to emphasize things I think are "missing" but overall I like Visual Studio .NET. I'm helping out with a project right now to get back into the swing of things, which is definitely a lot easier than starting from scratch! Stay tuned.

Posted at April 30, 2003 at 03:15 PM EST
Last updated April 30, 2003 at 03:15 PM EST
Comments

CVS support? In a Microsoft product?

Jesus Christ man... :)

If I recall correctly though, .Net does integrate fairly well with SourceSafe..

» Posted by: Peter at April 30, 2003 09:43 PM
Google
 
Search scope: Web ryanlowe.ca