MWPSK and Godaddy - v1.3.0

Topics: Developer Forum
Jul 28, 2010 at 1:27 AM

Shared hosting on Godaddy doesn't give the best results with MWPSK, because the virtual directory becomes part of the url. For example, a stock install of the home page for my site would be http://www.geekfrog.ca/geekfrog/homepage.aspx.

This is due to using a virtual directory - a great way to pay for only one hosting account with Godaddy while hosting multiple domains.

OK there are a few reasonably simple changes for version 1.3.0 to remove the extra virtual directory from your URL. I am sure there is a better way, and with cleaner code, but this works. Drop me a line and I'll update the article based constructive feedback.

http://www.geekfrog.ca/BlogSearch.aspx?tag=Godaddy

Jul 29, 2010 at 5:52 AM
Edited Jul 30, 2010 at 7:36 PM

I have to disagree with this method. I know it works etc (or does it?) but best practice is to configure the applications IIS headers, Perhaps it can't be done on the shared hosting offered by Godaddy.

If you have the need to install in a virtual directory then I would reccomend leaving it that way.

The reason for this being bad practice is urls that get index/linked to your site (as they appear in the browser) may be like www.MySite.com/Default.aspx (where Application A should reside, the default site for your domain) where its actual location it should be pointing to is www.MySite.com/Directory/Default.aspx (Application B), now you have a site in www.MySite2.com/Directory2/Default.aspx (Application C) Both use your method to remove the directory. user clicks in google search and is actually taken to www.MySite.com/Default.aspx now whos handling the mapping?

Not only that what about the site that lives in the root?

This kind of configuration should be left dealt with in IIS.

Jul 29, 2010 at 4:08 PM

@SpiderMaster - I agree its not an idea solution. However Godaddy does allow hosting of multiple domains in the same hosting account and for the most part this works fine. Your example assumes the same URL for all the Applications, which is not the case here. The issue is that the combination of MWPSK and Godaddy do not play well together. 

I am  just looking for a workable solution.

Many applications ask you to define the "base" for the website (http://www.MySite.com) and use that to build the URL's. MWSPK uses Server.MapPath, which tends to not have the intended result in the GoDaddy shared virtual host environment.

I have tried configuring IIS and DNS in the Godaddy world and have not yet been able to make any significant progress.

Jul 29, 2010 at 4:31 PM

@SpiderMaster - The Geekfrog Domain IS currently pointed to the Virtual directory, as you suggest and the results are the same. The Virtual Directory is included in the path. So unfortunately your idea doesn't pan out.