On Nov 14, 2005, at 20:41, Young, Jason (GE Infrastructure) wrote:
> We would like to have a file that users will have on their machine
> (web.config) that should be different than the master copy under
> source
> control. Basically, that file specifies which database to connect to,
> and users want to be able to connect to other databases. However, in
> the "master" copy, we need to connect to a specific database every
> time.
[snip]
> 1. Have another file called "Release.config" that gets renamed to
> "Web.config" during the build process. Only release.config would be
> under source control. Users would have a local web.config that
> they can
> edit as they please. The only problem is that users would have to
> copy
> release.config to get their local system running.
[snip]
I believe that's generally how people solve that problem. I think
it's pretty easy... you either have a script that you run after
checkout to copy the file and set up the environment in any other
ways necessary, or you can have the system print out an error message
if Web.config doesn't exist, explaining what file to copy and what to
edit.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 14 21:05:33 2005