I have an ASP.NET web application that needs to be rolled out to a
number of clients.
The functionality is the same in all applications, but each client has
its own database.
At the moment, I have one application per client, but most of the
files in the applications are the same, so this is not ideal from a
maintenance point of view.
The only differences between the client applications are:
- Different XML files related to each client
- Different database connection string
- Different application settings
All these differences can be handled from the web.config file.
I want an alternative solution that will reuse the common files, while
running each client's files as a separate application, under the
control of a separate web.config file.
Having a different application for each client allows for security
management across client apps, e.g.:
If I request a file with the URL:
http://www.myapp.com/client1/logon.aspx
I will log on to the application, and then browse to...
http://www.myapp.com/client1/home.aspx
and see content related to client 1.
And if I then request a file with the URL:
http://www.myapp.com/client2/home.aspx
the application will then detect that the user does not have an active
session variable for Client2 and will redirect to Client2/logon.aspx
Recoding of the application or consolidating the databases are not
options at this stage.
Can IIS handle this type of scenario, if so how do I set up my
applications in IIS to implement this?
TIA.