Building smarter connectionStrings for use Live / Local

views:

answers:

Building smarter connectionStrings for use Live / Local

Currently we are running multiple Sitecore projects. Whenever the projects go live we create new repositories in our subversion system. The downside in this case is, that when we go live we edit the connectionstring obviously, so that the connectionstrings correspond to the live servers instead of our local servers we run on. When a person that is joining our project now gets the repository from our SVN system, he will get the project with the live connectionstrings, which will result in alot of errors and frustration while I think this can be done way more efficiently. My question is:

How can I setup this construction that I can choose wheter I am working live or local, so that my project automatically will use the correct connectionString settings?

+3 A:

I'd strongly suggest you only check in safe connection strings, so nothing to a production environment. You'll run into serious trouble sooner or later.

Most companies change the connection strings in their deployment process, either manually (after copying the binaries to the production server) or automated (in a build script).

Gerrie Schenck 2010-03-04 12:57:35

Paddy 2010-03-04 12:59:40

Why will i run into serious problems when checking in my life connectionstrings?

Younes 2010-03-04 13:00:07

Can't accidently edit live data, as it's a dedicated server and it's using the 127.0.0.1 (local) adress

Younes 2010-03-04 13:00:34

In your question I read "which will result in alot of errors and frustration", so my answer also applies to this.

Gerrie Schenck 2010-03-04 13:05:52

I understand, but what I meant was the frustration of people having to change those connectionstring settings everytime.

Younes 2010-03-04 13:07:37

ansaurus

tags:

views:

answers:

Building smarter connectionStrings for use Live / Local

related questions