Visual Studio 2005
Caution, programming geekery ahead.
I’ve been using this a couple months now. I’ve got to tell you, it has got to be the worst official release I’ve ever seen from Microsoft. Anyone that uses computers on a regular basis knows what a big thing that is to say considering Microsoft’s track record. To be fair, yes Microsoft does make some great stuff, and it is pretty amazing the amount of hardware their software will run on. That said, I will commence with the bashing.
We all know how bad some of the little ins and outs of MS products can be. We know how buggy, or downright unstable some releases are. This thing takes the cake. It has more bugs than the everglades, and is less stable than an RV in a cat 5 hurricane. Honestly I don’t know how this got released, and imagine the man responsible is collecting unemployment currently. We have it installed on 4, maybe 5 high end MS spec workstations here. On at least two the development environment and compiler regularly crash. These are well maintained machines, completely up to date both hardware and software wise. I seem to be one of the lucky ones with how well it runs on my system. Wait, I kind of misrepresented that, let me try again. I seem to be one of the lucky ones because it only crashes a couple times a day on my system. It still crawls.
Crashing aside, they’ve added a ton of nice features, which you can’t disable, some of which make editing a flat text file a laborious process that involves a lot of waiting. One of my favourite new features is the “You can’t work on the screen you were just working on a second ago for no reason at all” feature. What this does, is when you’re designing a form and either switch out of the screen, run the program, or maybe edit some code behind the screen, you suddenly can’t view or edit it anymore. This happens near-instantaneously, I mean seriously blinding speed. At least there’s some optimization somewhere in this suite! But not all is lost, the solution is simple: Close all design mode forms, close the code behind form for the one that is acting up, rebuild your project. If that doesn’t work do the same, close visual studio, try that again. If that doesn’t work do the same, delete the binaries of your project and the output folders, open it back up and try again. If that doesn’t work go get coffee and sob into it for about 20 minutes, it should have fixed itself by then.
I’m not even kidding. It actually does kind of fix itself at random.
So why am I bothering to use this? Because it’s the latest from microsoft, and that’s leverage we can use in advertising our product. MS loves early adopters, and they will help you promote your software. It really does have some nice features that I look forward to using, but until a service pack is released I am actually being exponentially more efficient taking the time to type up a rant in my blog than I am actually trying to develop software with it.
Notice: Undefined index: oid_skip in /var/www/vhosts/makesitgood.net/httpdocs/wp-content/plugins/openid/logic.php on line 1080
1 Comment
» Leave one of your ownNo comments yet.
RSS feed for comments on this post. TrackBack URL
Leave a comment