Hi think you saw this in Don Kiely session "Extreme Exception Handling in ASP.NET"

If this is the right sessions, you will have access to the video of that session soon. We will release 5 videos of sessions done at DevTeach to all attendees of DevTeach 2004.

>There are features in VS.NET to do this.
>
>Copy the Config file and rename it as follows
>Change the name to release.config
>Modify the contents of the file to be your relase settings.
>when you are ready to build go into the configuration manager and set your settings as Release.
>This will then build using your release.config file versus your debug.config file.
>
>I saw this at devteach and it was pretty neat.
>
>I think i remember this correctly, but i am going from memory.
>
>Hope this works.
>
>--> Shawn
>
>
>
>>>There are usually only a couple of things that need to be specifically set for the server like connection strings and it's easy enough to do this 'on the fly'. it helps to write down what these 'couple of things' are as part of your deployment documentation.
>>
>>I've ended up just copying/modifying the web.config file as I moved & tested my apps. Then I'll just comment out the original section in the web.config so I know which need to be modified during deployment, eg.:
>>
>>

>><!-- Test server config
    <add key="SQL\Connection" value="server=DEVSQL;uid=UserIDGoesHere;pwd=PasswordGoesHere;database=Dev_SQL;"/>
    <add key="SQL\DataAccessClass" value="DataAccessSql"/>  -->
>><!-- Live server config follows -->
>>