Thanks for your response. I do have a database, and that is the straw that broke the camel's back. On September 5, I could access it. On September 10, I could not .The ISP keeps telling me the connectionString is wrong. First they said the error was in web.config, which did not even have a connectionString value until I added it. That didn't fix it. Now they are saying I need to change the applicationmanagement.dll to update its connection string. I have no idea why they think such a value exists in this .dll. To me it sounds like a copout to avoid the responsibility for whatever they did that changed the environment after September 5.
The database contains both a membership list and protected documents that you retrieve from the database once logged in. I presume I need the ISP's cooperation to copy my database in full, yes? Thanks. Ken On Sep 23, 2:17 am, Varun Jain <[email protected]> wrote: > Hi Ken, > > I hope so, your question is about moving from one hosting to another > hosting. > > It's depends on the website that what all resource does it use like, > Database, etc. > > If it's only a simple website without database and all (only webpages), it's > a pretty easy task by moving the file to another hoster. > > But if it has DB, then u have to move the database from one host to another > and change the connection string accordingly. > > Apart from this, you have to change the nameserver's on your domain to point > to your new webhosting provider and your new site. > > For instance, a websitehttp://www.webasystant.comand some one like to host > with it. So, he just have to change the nameserver's to NS01.webasystant.com > , NS02.webasystant.com and delete the previous nameservers. This means that > now the website is pointing to the server's with the DNS name NS**. > webasystant.com > > For any further help, do contact me!!! > > Regards, > VJ > > On Thu, Sep 23, 2010 at 7:08 AM, OccasionalFlyer <[email protected]> wrote: > > My ISP has been so unreliable this year that I would like to move my > > web site elsewhere. Since I'm not an expert by any means in ASP.NET > > (definitely still a newbie), I don't know how much work this would > > be. What would be involved, beyond the mechanical part of copying > > files, to move my site to a different ISP? Thanks. > > > Ken
