Knowledgebase

One of the problems we encountered from a multi-server point of view, is that the admin directory should really not be exposed on the website at all.  We can use IP restrictions, Integrated authentication, and folder permissions to do this... but it would be much easier if admin was a totally independent application (with it's own BIN).  We tried to make a virtual web server just for admin, but it won't function because root BIN and web.config need to be there.It would be great if it were a separate app because:

• We could put the admin on an internal server, have it manipulate the database
• Externally there is no admin web directory at all so there's nothing to configure or protect.

Not a show stopper by any means, but it's a nice to have for a larger installation.  Of course it would mean that the image and custom HTML uploads would need to go in the database (or be synced to the external server).