My Probably Unpopular Opinion of Edit and Continue

I don't see what the big deal about edit and continue in VB.NET is all about.  Sure unit testing will save your soul, but I am willing to be that 99% of all VB.NET applications aren't using unit testing, and probably never will.  Why?  They probably aren't developing that many classes.  Does that make them bad people or bad programmers.  To me, no.  They are simply putting together applications from existing components that have been unit tested.  How would you exactly unit test a webform? 

Almost every class library I've written has been in C#.  Why?  I think the language lends it self better to writing class libraries.  XML documentation, operator overloading, all that good stuff.  Plus, in the future it will support creating generics and VB.NET might only support consuming them.  Looking more and more like the people the main chunks of apps will be using C#.  Sure a lot of that will be in whibdey for VB.NET, but how many VB.NET developers will be using it?  Not many.  Your typical Mort needs to get 5 seperate small to medium sized projects done in the next three months.  

As for developing UI's, my choice 1000% of the time will be VB.NET.  As for developing simple applications, VB.NET.  It just is easier to work with.  And edit continue will make it easier to work with, thus making VB.NET better.  Hooray!

2 Comments

  • Dangit, walked right into that one. I even knew it existed. My brain is already on the weekend :)

  • I admit my vb.net classes aren't unit tested; it'd be nice to have the time! I must be an exception too to using classes in VB. There's ~ 130 in my current project ;-) Edit and Continue would have a hell (or heaven!) of a difference to vb.net. My app's in asp.net so the slow startup of the app on making small changes is a killer, but still being able to modify property values etc within the app does also help. Just means making a few more modifications before each build...

Comments have been disabled for this content.