Migrating from Development to Production...

Several ways to do that

1)

a) Store the connection string in the web.config file
b) Change your application to pull the connection string from the web.config
c) Config VS.net to NOT deploy the web.config file. To do this, bring up the project property page by right clicking on the project. Goto Configuration Properties -> Deployment. Select Web.config in the override files dropdown.

OR

2) create a host file entry on your local box to point the sql server name to your local machine

eg. mssql01 -> 192.168.1.2

Hope this helps.

quote:Originally posted by pg

I'm using VS.Net. Using the "Copy Project..." command works great to upload from development to production.

Now...I want to move another project to DASP - using SQL/Server. Currently I have to change all of the connection strings (using a text processor) and then ftp the files over - and then do a rebuild on the host machine.

Is there a way to make this migration easier?

Thanks in advance!

(DASP is great, eh?)
</blockquote id="quote"></font id="quote">