Publish ASP.NET 2.0 site

[Eric]

I have what is hopefully a quick question. I want to have a quick and
easy method for deploying my website to our test environment. I need
something to do nearly the same thing as the "Publish Web Site" option
under the build menu, except I don't want it to copy over the
web.config file. There are a few settings that need to be different,
so I want the publish process to leave the web.config file alone. What
is the easiest way to do this?

Thanks,
Eric

[Laurent Bugnion]

Hi,

Eric wrote:

I have what is hopefully a quick question. I want to have a quick and
easy method for deploying my website to our test environment. I need
something to do nearly the same thing as the "Publish Web Site" option
under the build menu, except I don't want it to copy over the
web.config file. There are a few settings that need to be different,
so I want the publish process to leave the web.config file alone. What
is the easiest way to do this?

Thanks,
Eric

You could publish to a local filesystem folder, and then FTP everything
to your site except the web.config.

HTH,
Laurent
--
Laurent Bugnion, GalaSoft
Software engineering: http://www.galasoft-LB.ch
PhotoAlbum: http://www.galasoft-LB.ch/pictures
Support children in Calcutta: http://www.calcutta-espoir.ch

[Peter Bromberg [C# MVP]]

If you store your settings in the <appSettingssection, you can use the
<appSettings file="xxxx"
directive to keep those settings in a separate file, which can be different
for both production and development.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Eric" wrote:

I have what is hopefully a quick question. I want to have a quick and
easy method for deploying my website to our test environment. I need
something to do nearly the same thing as the "Publish Web Site" option
under the build menu, except I don't want it to copy over the
web.config file. There are a few settings that need to be different,
so I want the publish process to leave the web.config file alone. What
is the easiest way to do this?

Thanks,
Eric

[Eric]

That is basically what I am doing now. For convenience sake I am
wondering if there is a way to remove the second step.

Laurent Bugnion wrote:

Hi,

Eric wrote:

I have what is hopefully a quick question. I want to have a quick and
easy method for deploying my website to our test environment. I need
something to do nearly the same thing as the "Publish Web Site" option
under the build menu, except I don't want it to copy over the
web.config file. There are a few settings that need to be different,
so I want the publish process to leave the web.config file alone. What
is the easiest way to do this?

Thanks,
Eric

You could publish to a local filesystem folder, and then FTP everything
to your site except the web.config.

HTH,
Laurent
--
Laurent Bugnion, GalaSoft
Software engineering: http://www.galasoft-LB.ch
PhotoAlbum: http://www.galasoft-LB.ch/pictures
Support children in Calcutta: http://www.calcutta-espoir.ch

[Eric]

I need to change 1 appSetting and 2 connection strings. I'm wondering
now if there is a way to detect a release build. Since publish builds
for release, I could have it use different settings in the web.config
based on that.

Peter wrote:

If you store your settings in the <appSettingssection, you can use the
<appSettings file="xxxx"
directive to keep those settings in a separate file, which can be different
for both production and development.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Eric" wrote:

I have what is hopefully a quick question. I want to have a quick and
easy method for deploying my website to our test environment. I need
something to do nearly the same thing as the "Publish Web Site" option
under the build menu, except I don't want it to copy over the
web.config file. There are a few settings that need to be different,
so I want the publish process to leave the web.config file alone. What
is the easiest way to do this?

Thanks,
Eric

[Laurent Bugnion]

Hi,

Eric wrote:

I need to change 1 appSetting and 2 connection strings. I'm wondering
now if there is a way to detect a release build. Since publish builds
for release, I could have it use different settings in the web.config
based on that.

I think it's a possibility.

The compiler variable DEBUG is only defined for Debug build, and is not
defined for release. Additionally, you can use the Configuration manager
in Visual Studio to define more variables if needed.

#if DEBUG
// Use Debug setting
#else
// Use release setting
#endif

You could also test if the Request path is for "localhost" or for
something else, in which case it would be the production server.

HTH,
Laurent

>
Peter wrote:

>If you store your settings in the <appSettingssection, you can use the
<appSettings file="xxxx"
directive to keep those settings in a separate file, which can be different
for both production and development.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Eric" wrote:

>>I have what is hopefully a quick question. I want to have a quick and
easy method for deploying my website to our test environment. I need
something to do nearly the same thing as the "Publish Web Site" option
under the build menu, except I don't want it to copy over the
web.config file. There are a few settings that need to be different,
so I want the publish process to leave the web.config file alone. What
is the easiest way to do this?

Thanks,
Eric

--
Laurent Bugnion, GalaSoft
Software engineering: http://www.galasoft-LB.ch
PhotoAlbum: http://www.galasoft-LB.ch/pictures
Support children in Calcutta: http://www.calcutta-espoir.ch

[Eric]

Thanks a bunch, I think that will work.

Laurent Bugnion wrote:

Hi,

Eric wrote:

I need to change 1 appSetting and 2 connection strings. I'm wondering
now if there is a way to detect a release build. Since publish builds
for release, I could have it use different settings in the web.config
based on that.

I think it's a possibility.

The compiler variable DEBUG is only defined for Debug build, and is not
defined for release. Additionally, you can use the Configuration manager
in Visual Studio to define more variables if needed.

#if DEBUG
// Use Debug setting
#else
// Use release setting
#endif

You could also test if the Request path is for "localhost" or for
something else, in which case it would be the production server.

HTH,
Laurent

Peter wrote:

If you store your settings in the <appSettingssection, you can use the
<appSettings file="xxxx"
directive to keep those settings in a separate file, which can be different
for both production and development.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Eric" wrote:

I have what is hopefully a quick question. I want to have a quick and
easy method for deploying my website to our test environment. I need
something to do nearly the same thing as the "Publish Web Site" option
under the build menu, except I don't want it to copy over the
web.config file. There are a few settings that need to be different,
so I want the publish process to leave the web.config file alone. What
is the easiest way to do this?

Thanks,
Eric

--
Laurent Bugnion, GalaSoft
Software engineering: http://www.galasoft-LB.ch
PhotoAlbum: http://www.galasoft-LB.ch/pictures
Support children in Calcutta: http://www.calcutta-espoir.ch