S
saunderl
Hello Everyone,
I'm a lead developer of a ASP.Net site. We have over 150
"applications" running at our site. Each application is a "Solution"
in VS. When we roll to test and production, the main dlls are rolled
to the sites single bin directory and the aspx, asmx etc files are
rolled to various folders on the server.
Now with ASP.Net 2.0 they changed everything. No longer is a web
project a project, its a SITE. The dll names are mangled and renamed
every time its published. What used to be just references are now part
of the soruce control, as if I want compiled dlls in sourcesafe!
All told, after two weeks of looking to move to ASP.net 2.0, I'll have
to say that "It will not happen!" They have made managing a large,
diverse site like ours impossible. Sure, Microsoft gave us lots of
"Wiz Bang" stuff for the kiddies, but really screwed the large scale
site developers, or so it at least seems to my team.
All told, I think that Microsoft REALLY screwed the pooch on this one.
L. Lee Saunders
I'm a lead developer of a ASP.Net site. We have over 150
"applications" running at our site. Each application is a "Solution"
in VS. When we roll to test and production, the main dlls are rolled
to the sites single bin directory and the aspx, asmx etc files are
rolled to various folders on the server.
Now with ASP.Net 2.0 they changed everything. No longer is a web
project a project, its a SITE. The dll names are mangled and renamed
every time its published. What used to be just references are now part
of the soruce control, as if I want compiled dlls in sourcesafe!
All told, after two weeks of looking to move to ASP.net 2.0, I'll have
to say that "It will not happen!" They have made managing a large,
diverse site like ours impossible. Sure, Microsoft gave us lots of
"Wiz Bang" stuff for the kiddies, but really screwed the large scale
site developers, or so it at least seems to my team.
All told, I think that Microsoft REALLY screwed the pooch on this one.
L. Lee Saunders