Hi,

You can install it either as a root level site or in a sub folder below a root level site as an application. In either case the folder can exist anywhere on disk. If you want to install it as an app below localhost using your default web site, create a folder somewhere named mojoportal or whatever you like. Copy the "contents" of the mojoportal wwwroot folder in our package into that folder. Right click your default web site and choose add application, browse to the folder, configure your app pool etc. If you have another .NET app running in the root of the default web site you may get web.config conflicts but these can be resolved as indicated in the first item of our developer faq. Then it will be under localhost/whateveryounamedtheapp

However if you're planning to populate content into the site and later move it to hosting as a root level web site then you should probably install it locally as a root level web site because of issues mentioned in Moving an Installation of mojoPortal to a different server. If you already have stuff running in the default web site just create another site and use a host name. 

See also:

• Manual Installation Recipe for IIS 7.x and .NET 4
• Adding a Host Name to the hosts file for local testing
• Manual Installation in IIS 7.5 Video
• Installing mojoPortal Using the Platform Installer
• Hosting Multiple Sitesd in a Single Installation of mojoPortal Using Host Names video

Hope that helps,

Joe

If you install mojoPortal in the root of default web site and you have other .NET apps running in folders beneath it then there will still be issues caused by web.config inheritance, ie the mojoPortal Web.config might cause problems in those other apps, though it could be mitigated as mentioned in the first item in our developer faq.

I think the easiest thing for you local environment is to create a new web site instead of using default web site, and add an entry in your hosts file as discussed in the article Manual Installation Recipe for IIS 7.x and .NET 4.

ie you would add this in your hosts file:

127.0.0.1 mojoportal

then use mojoportal as the host name in the new IIS web site, then you would access the site using http://mojoportal instead of http://localhost

Hope that helps,

Joe

If you mean the other apps you have running under the default web site in folders, no, those would still be under localhost since they are under the default web site not the newly created one.

Hi Dave,

Please see the "Hosting Multiple Sites on One Installation" documentation. It sounds like you want to create a single mojoPortal site in IIS and then set it up to use Folder Based Multiple Sites.

HTH,
Joe

Hi Dave,

A single installation of mojoPortal can do either multiple sites based on host names or multiple sites based on folder names, it cannot do both. You would need two installations one for folder sites and one for host name based sites.

For folder based sites the first site must be a root level site it cannot run as a subfloder beneath an IIS web site so you would first get it working at http://mojoportal/ ot http://whateverhostnameyouchoose/ using previosu instructions I've given you

and even for host name based sites it doesn't make sense to use subfolders so host name based mutliple sites needs to be first installed as a root level IIS web site., again with instructions I've given you you would first get it working at http://mojoportal/ or really at http://whateveryouwant/

Then if you are going with host name based sites you need to add additional host names to your hosts file for each one, ie

site1 127.0.0.1

site2 127.0.0.1

whateveryouwant 127.0.0.1

and also add those host names in the new IIS web site as host names otherwise IIS will resolve any host names not specifically assigned to a site will resolve to the default web site which has no host names

so after you create the site depending on which approach is configure you will see in site settings either a tab for assigning host names to a site in mojoPortal or assigning folder names, you enter the host name or folder name there.

if using host names then you access the sites using http://site1/ or http://site2/ ie whatever host names you used.

if using folder sites you access the sites with

http://mojoportal/foldername/Default.aspx

or

http://whateverhostnameyouused/foldername/Default.aspx

Hope that helps,

Joe

Hi,

But now the question arises as to how I can edit the hosts file on the production server at Arvixe. Hmm. I'll have to check with them, I guess

No, what I've shown you is a way to do it on your dev machine without use of a DNS server. On the internet host names are resolved to ip addresses by DNS servers and you have to use real ip addresses not the loopback address 127.0.0.1 which on all computers points to itself even if tha machine has no network card at all and you can't do it with host files, that would require being able to add entries to the host files of every single computer that accesses the internet.

So you need a site with a fixed ip address ideally a dedicated ip address not shared by other sites at the host, and youneed DNS settings on a DNS server that map host names/domain names to that ip address.

I noticed in your notes about the hosts file you put the name first followed by the 127.0.0.1 but in the file on my computer it is the reverse.

Yes, I typed that incorrectly (I just now fixed in the documentation, it was shown more clearly in the screen shot), the ip address goes first. But as mentioned above you need to understand about the loopback address 127.0.0.1, then you'll get the joke on this think geek t-shirt.

Hope that helps,

Joe