I have spoken to GoDaddy several occasions but nobody there knows what they are speaking about. I am developing a simple site for any company who uses GoDaddy Home windows Hosting that is shared and Let me create the project using MVC version 5.
The very first time the guy stated he had not heard about MVC which GoDaddy does not support it. The 2nd time I known as they stated they merely support MVC on devoted hosting and that he wasn't sure about MVC 2 particularly. The 3rd time I known as the guy stated I possibly could run MVC 2 on hosting that is shared.
Anybody that really practical knowledge know?
Like a current GoDaddy customer I will tell you they have IIS 7 servers on Home windows 2008.
Also, ASP.Internet MVC 2 works. To really make it work you have to make certain the following libraries have been in the bin directory:
Make certain you place the Copy Close to true on individuals 2 libraries and make certain you upload the BIN directory.
Here is a straightforward site I designed for our neighborhood Kub Kar Races (Pinewood Derby for that People in america). It's located on GoDaddy and was built utilizing a Beta for MVC2 (unsure which any longer).
I first got it working yesterday.
The important thing what exactly you need are:
make certain you don't have any code that breaches Medium Level security
your key MVC DLLs are setup as
"Copy Local" = truewithin the qualities pane
your IIS configurations should be integrated rather than classic
Best of luck
(See my other publish : ASP.Internet MVC inside a subfolder (only) on godaddy)
MVC 2 needs IIS 7 ... You may be on IIS 6 at GO Dad ...
MVC as they are should be run in IIS7. I don't know what version of IIS GoDaddy is applying but odds are it's IIS6. If that's the situation, you are able to still do MVC your routes must range from the .aspx extension. So, in case your URL appears like this:
you have to alter the route to ensure that the URL appears like this
You will find some posts that suggest utilizing an .MVC extension and adding that extension to IIS but it's not necessary to do this if you are using an extesion that IIS already knows to map to ASP (like .aspx)