VS.NET 1.1
Well the MSDN images came down a lot easier than the actual VS.NET installer did. Honestly, I'm only semi-excited because the final beta has been so stable and I haven't used 1.0 since late last year. The redist. build number doesn't look like it changed and it actually hiccupped on one of the 2K3 servers I put it on. Wouldn't give up one of the tlb files even on reboot, so we'll see what's going on with that. VS.NET still can't project copy to one of my 2K3 boxes, claims it's not running ASP.NET 1.1. Lies. Isn't able to set virtual permissions on the other one, but that's no big deal. We'll see if this is fixed when everyone's running the final releases.
I looked at CodeSmart from
AxTools earlier this evening. Pretty nice, I installed it a while ago and never really used it on my primary machine, it's got like a 3-hour expiration period or somesuch. So I put it on another box and it seems like it has a lot of useful functionality, but with these kinds of tools I have to use them regularly for a stretch to see if it's love or hate. I want to do away with the half-ass macros, the bad VA.NET tpl substitutions just to automate adding a member field backing a property accessor exactly the way I like it. Type type typitty type. Oh well. At $189 for a single license, CodeSmart isn't worth taking a flyer on. I hate trialware with a draconian eval period. Man do I miss CodeRush (Eagle Software claims Sidewinder is going to blow VS.NET away and when Delphi.NET is release C# will be exposed for the fraudulent language it is--lol. There's a Fry's somewhere in Scotts Valley that needs a restock on the Kool Aid aisle).
Off for more interviews tomorrow. Should be the usual rollicking good time. ;)