I have recently started using a shared-host for my clients so see project progress or to play with a new technology for myself. I seems like every time I deploy a new project that runs fine locally, I run into something new on the shared-host.

Do you have a shared hosting deployment checklist?

What are the common problems you run into when deploying to a shared host?


Community Wiki, please

Written by Graviton

Please don't continuously edit the question with the current top ten list every time someone answers or votes. We can see the "list" by looking at the answers sorted by votes.

Written by gnovice

This is a community wiki, edit what you don't like.

Written by rick schott

The point is not editing too much. There isn't really a need for you to keep a list in the question that you constantly update. The ordering of the answers by vote essentially is the list. Every time you edit the question, it bumps it to the top of the active list, which gets obnoxious if it's done too often (and for unneccessary reasons).

Written by gnovice

@gnovice - this isn't true I don't believe. It can only get bumped every so often.

Written by womp

Accepted Answer

Medium Trust. If you are developing code to go into a shared host, you should set your local application to run in medium trust otherwise you can almost guarantee you'll get security issues with code that executes fine in full trust but dies in a medium trust environment.

This MSDN article explains about medium trust in more detail:


Written by lomaxx
This page was build to provide you fast access to the question and the direct accepted answer.
The content is written by members of the stackoverflow.com community.
It is licensed under cc-wiki