From the ASP era to the ASP.NET era, I feel all, but one thing, I have never released:
For a large-scale website that is often changed:
If it is an ASP, if I add, change a page, just add, update this page, will not affect the run of the entire website, including session.
But it is .NET, you can minimize system coupling, separating your business logic, but this codebehind is really a trouble, such as adding a page (you have to involve codebehind), you have to originally huge DLL Re-build, and re-XCOPY, so all sessions will be lost! In this way, each re-deploy will be forced to go online late in late night (so that the customer complaint may be less). Painful
Why is the Web layer must write a DLL, can be compiled, deployed according to its business features. The most important thing is: After a web.dll compile deployment of a business function, it will not affect the entire site, which is .NET does not recover the field operation? Or can the entire session come from the old program domain COPY to the new program domain?
In confusion. . . . . . . . . . .
