Hosting companies tend to create bare bones sites with most features disabled (to protect there servers). It works for most clients but for people building sophisticated .NET applications it can be a struggle.
Also, if you are developing on XP or Vista using Visual Studio, they have less restrictive settings and VS does a lot of things behind the scenes on the local system you may not be aware of. So, a site might work locally but not on production.
I'd recommend that you try to get your site running on a local copy of Windows 2003/2008 Server first to troubleshoot and make sure you understand your settings.
For example, I don't have a clue what errors you are receiving.
Main Topics
Browse All Topics





by: skiaboxPosted on 2008-09-07 at 03:10:27ID: 22410741
I see that all the needed tables are online in the database.
Both the local databases (Balloonshop and ASPNETDBMDF) are merged in one remote database (BalloonShop)
with BalloonShop tables appear in the dbo schema and the ASPNETDBMDF table appear in the remote BalloonShop database in
the same schema (for example dbo.asp.net_Roles).
I searched the data and they are ok.