Click here to Skip to main content
15,893,668 members
Please Sign up or sign in to vote.
4.00/5 (1 vote)
See more:
Hi!

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.

Alysson Moulin
Posted
Updated 12-Mar-13 2:23am
v2
Comments
Zoltán Zörgő 12-Mar-13 8:28am    
Sorry, but the original solution was a clear nonsense. Changing to almost anything than that is a benefit.
fjdiewornncalwe 12-Mar-13 9:05am    
Well said.
Alysson Moulin 12-Mar-13 11:16am    
Thank you so much! Taking this oportunity, I must suggest a solution to the initial problem: How to share a session between two or more virtual directories? I read about managing the session inside a SQL database or use a cookie to store the authentication information and make the applications consume it. In your opinion what is the best way to solve the problem? Is there another solution?
Zoltán Zörgő 12-Mar-13 13:48pm    
Ok. There are several major approaches, without going into details
1) You can use any off-process session management feature to share session even between farm servers
2) If you use domain cookie, all subdomains or virtual directories can read this cookie. You usually can send authentication cookies out, but session cookies are also cookies.
3) Google on ASP.NET SSO (single sign-on). You will find several implementations and method.
Alysson Moulin 13-Mar-13 11:23am    
Thank you for your reply. I will search about it!

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900