We have a legacy system that is built in classic ASP. As we go to asp.net, we create web applications ourselves because we migrate the old stuff to .net and add new functionality to the system. I would say that 30% of them will share the same library, they will load the DLS. (All apps share the same app pool)
My question is, what are the pros and cons of this approach? Would it be better to have an application rooted?
I'm not really looking for a specific answer, just curious what you guys do and why?
Thank you very much
I will place things that logically Examples: Under the IIS, the essential components for a website or webpage can be considered as a logical group, so it needs its own app pool.
Whatever is different, it should have its own domain with an app pool. But, IMHO, I think it is a decision call based on the nature of the app and if it has any dependency ... etc. You know better than any system, so why should it look everything from 20k foot footage divided logically?
Example Scenario: If you have an app to reset through IIS, will it affect others (due to an app requiring another IIS reset) If this is not a big deal If not, why not (lump it together with others). If it is a big deal, keep it separate so that it does not depend on any external.
Comments
Post a Comment