By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,296 Members | 1,473 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,296 IT Pros & Developers. It's quick & easy.

Web.config.exclude

P: n/a
Hi,

Am currently in the process of migrating a whole heap of v1.1 ASP.NET
solutions to v2.0, and would be interested to know what others are doing
about excluding web.config from projects.

In v1.1, it was quite usual to exclude web.config from the project so that
it wouldn't get deployed to the live site along with the rest of the aspx
etc files and the bin folder. Typically (for me, anyway!) this was because
the web.config would contain lots of appsettings values which were different
in the development environment, the testing environment and the live
environment e.g. database connection strings etc. Excluding web.config from
the project meant that it didn't get deployed with the rest of the solution
so that deployment wouldn't overwrite the file on the other environments.

Excluding web.config in ASP.NET 2 renames it to web.config.exclude, which
causes debugging to fail.

What is the accepted wisdom for overcoming this in ASP.NET 2?

Mark
Dec 2 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
No-one got any ideas...?

"Mark Rae" <ma**@mark-N-O-S-P-A-M-rae.co.uk> wrote in message
news:OT*************@tk2msftngp13.phx.gbl...
Hi,

Am currently in the process of migrating a whole heap of v1.1 ASP.NET
solutions to v2.0, and would be interested to know what others are doing
about excluding web.config from projects.

In v1.1, it was quite usual to exclude web.config from the project so that
it wouldn't get deployed to the live site along with the rest of the aspx
etc files and the bin folder. Typically (for me, anyway!) this was because
the web.config would contain lots of appsettings values which were
different in the development environment, the testing environment and the
live environment e.g. database connection strings etc. Excluding
web.config from the project meant that it didn't get deployed with the
rest of the solution so that deployment wouldn't overwrite the file on the
other environments.

Excluding web.config in ASP.NET 2 renames it to web.config.exclude, which
causes debugging to fail.

What is the accepted wisdom for overcoming this in ASP.NET 2?

Mark

Dec 4 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.