I'm trying to put together an auto-provisioning process so when a user signs up, s/he gets an instance of blogengine.net. So let's say I have the following structure in IIS7
What I'm currently doing is that I'm creating a directory under "public/<customer id>" relative to my root and I copy and paste the whole shabang of files and directory of blogengine.net to that location. The problem is blogengine.net
doesn't work (won't show up) unless and until I go to IIS manager MMC and add the public/<customer id>/blog directory as an "Application." AFter I make the directory an application, then it works. If I don't do that and try to browse
that location, I get
Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.
Line 7: </configSections>
Line 8: <BlogEngine>
Line 9: <blogProvider defaultProvider="XmlBlogProvider">
Line 10: <providers>
Line 11: <add name="XmlBlogProvider" type="BlogEngine.Core.Providers.XmlBlogProvider, BlogEngine.Core"/>
I tried adding a virtual directory using "appcmd.exe add vdir blah blah" and while it says that the vertial directory has been added, the blogengine doesn't show up. Again, but if I go to IIS7 manager and right-click and do a Add Application
on that directory, everything works.
The whole point is to create an instance of the blogengine.net for each user so they'll isolated from each other in as much as hands-off fashion as possible. It would have been nice if I could factor out all the common elements from all the instances
and just specify the attrtibutes but for now, I can live with each having their own set of files if I can get it to work. Any and all suggestion is apperciated and thank you in advance. Please let me know if I can clearify anything.