work/MS bitching
If there is one complaint I have with Visual Studio 2005, its that they completely fscked up the whole "WebSite" project paradigm. Its now a Folder. A friggin FOLDER. And NOT EVEN A RELATIVE PATH FOLDER. FSCKIN A MICROSOFT, what were you THINKING?!? >_<;;;
Grrrr....
You can sorta get around the fact that you no longer have a project file by assigning the "WebSite" (and yes this includes WebServices [grrr]) to a solution file, and assigning its dependent projects there and such. But WHY ISNT THE WEBSITE PATH RELATIVE? I have to have something to check into CVS that I can deploy! ;_;
Sorry for the yelling... Had to vent... Much hate for this whole new paradigm when working on webservices in .Net v2.0. *sigh* Don't get me wrong, there's a lot of good things in .Net 2.0 like generics and reflection and partial classes (and I cant wait for this whole XNA games development studio thing [is in beta now] which Matt and I want to look into once my work hell is over).
Grrrr....
You can sorta get around the fact that you no longer have a project file by assigning the "WebSite" (and yes this includes WebServices [grrr]) to a solution file, and assigning its dependent projects there and such. But WHY ISNT THE WEBSITE PATH RELATIVE? I have to have something to check into CVS that I can deploy! ;_;
Sorry for the yelling... Had to vent... Much hate for this whole new paradigm when working on webservices in .Net v2.0. *sigh* Don't get me wrong, there's a lot of good things in .Net 2.0 like generics and reflection and partial classes (and I cant wait for this whole XNA games development studio thing [is in beta now] which Matt and I want to look into once my work hell is over).