12 Feb 2007
26 Aug 2010
Link to this post
I am just evaluating sitefinity, so, please, excuse me, if my question is stupid.
We have found out that it is more efficient to maintain only one app for all our clients rather than multiple instances of the same app.
So, I was hoping to have an option to have all our clients to use one website too. Currently for all other ASP.net applications we are passing applicationId to the application, which determines which database to go after for authentication, as well as for everything else. So, we switch connection to the database at run time, which allows each client to feel like they are going to their own application with their own master pages, authentication, styles and of course their own data.
Basically, I was wondering how can we achieve similar productivity with sitefinity. I am not sure yet, if we want to have different databases to serve different clients, but It would be nice to maintain just one application for all clients. Basically, each client should be able to manage its own images/templates, etc. Each individual client should potentially have a connection to his/her own information system database.
At the same time, it would be nice to have some templates,controls, etc shared between all of them. Basically, by releasing the app once, I want all the clients to get the updates. We will then setup aliases through IIS, so that
let's say client 1 will go to CLIENTOne.com, while really going to
website1. .?clientId=1, then client 2 will go to CLIENTTwo.com, while really going to
Does it make any sense?