Robert McLaws: FunWithCoding.NET

Frans seems to be getting awfully riled up over the backlash from his post. I can say this because I had this lesson taught to me as well: As a developer blogging in this community, you have a responsibility to clarify what is opinion and what is fact. What Frans effectively did is back up PeopleSoft's horrendously ridiculous comment that .NET is IT asbestos. By saying "ISV's: do NOT upgrade to Visual Studio.NET 2003! " you are sending not only a bad message to the community, but a message of opinion masked as fact. If versioning issues are your only reason, (pardon my bluntness) sorry but IMO, your reason is not good enough to justify such a harsh stance. The reason I can say anything about this is because I have been guilty of this before, and have since had to change my thinking.

Chris Sells ceases to make fun of VB developers. Also, Moon spins off into outer space. Film at 11.

Unfortunately my idea for rerouting assemblies to 1.0 programmatically does not work. The problem is that there is not currently a way to unload an assembly (to the best of my limited knowledge). If you could, what I would do is prevent it from trying to unload the referenced assemblies and load the 1.0 assemblies instead.

Scott doesn't like "C# Design Patterns". I can't say that I do either. It was horribly written and very hard to follow. I will be looking into Slavomir's suggestion very shortly.

tried out my code yet? I'd really like to know if it works.

Frans Bourma comments on the issues he has with VS.NET 2003, and even goes as far to say that if you are an ISV, you should not be building tools to .NET 1.1. Wow. That's a pretty rough statement. Well, I'm an ISV and I upgraded to VS.NET 2003 six months ago, and while it means that you have to exert a little more effort, the improvements alone are worth it.

I was looking through the pingbacks/trackbacks in my blog, and I found out that there are over 100 links to my quasi-rant on how .NET 1.1 is not an upgrade to .NET 1.0. WOW. That's kinda cool. Scoble's pretty popular, and he only has 16 readers . I think those same 16 read my blog, because all the rest are Google links.

Go to Tools... Options, then click the Debugger folder, select Edit and Continue, and make sure both checkboxes are checked for C# and VB. This way you can edit ehile debugging and not have the debugger get pissed off. You can also set whether or not the debugger will restart execution, warn you, or ignore the changes and continue debugging. One step close to Edit and Continue in VB..... still waiting tho.