Guys, in my company we have the scenario bellow:
Several applications published in the same IIS virtual directory, using the same "bin" folder to publish the DLL's and under the same application pool.
In a long time ago, in a galaxy far, far away, we had to do this because we wanted to share the same session on IIS.
But over the years, we gathered a lot of applications under the same virtual directory and started to face some problems:
- Everytime we publish a new dll, we shutdown other applications.
- I couldn't publish a 4.0 application without create a new virtual directory, so I had to implement a workaround to make it works.
- The applications share the same webconfig, so we can't create generic tags for them.
Now I have a chance to convince my boss to correct the situation. And this is why I need your help. I must point the benefits (performace, best practices, organization, etc) of this kind of change.
Could you help me, please?
Thank you in advance.