This one STILL bugs me no end... Anybody with a solution (other than adding all this crap to my path... I can do that) feel free to chime in.
1) Windows2003 is the bomb because it ships with .NET 1.1 baked into it.
2) If that's the case why don't I get access to all of the .NET command line tools automatically In other words, why can't I just hit start - run - cmd and then be able to run instalutil or gacutil etc I can't because they're not added to the path by default.... which seems strange if they're part of the .NET Framework, and the .NET framework is 'baked-in' to Windows 2003.
Stooopid marketers...
See... it's been a day. I KNEW nobody was reading this thing. *sniff*
Posted by: Michael K Campbell | April 28, 2004 at 01:20 PM