Comments on: Share ConnectionStrings between projects for each developer differently http://blog.mastertheteam.net/2008/10/share-connectionstrings-between-projects-for-each-developer-differently/ Jand writes about team development and Microsoft.NET Mon, 14 Jun 2010 20:05:51 +0200 http://wordpress.org/?v=2.8.2 hourly 1 By: Light http://blog.mastertheteam.net/2008/10/share-connectionstrings-between-projects-for-each-developer-differently/comment-page-1/#comment-1455 Light Mon, 07 Jun 2010 06:54:27 +0000 http://blog.mastertheteam.net/?p=33#comment-1455 <strong><a href="http://moysotik.ru/ http://rel" rel="nofollow">Даже не знаю</a>...</strong> Ссылки как то странно отображаются... http://rel” rel=”nofollow”>Даже не знаю…

Ссылки как то странно отображаются…

]]> By: Коля http://blog.mastertheteam.net/2008/10/share-connectionstrings-between-projects-for-each-developer-differently/comment-page-1/#comment-883 Коля Tue, 06 Apr 2010 23:39:55 +0000 http://blog.mastertheteam.net/?p=33#comment-883 <strong><a href="http://country-mp3.com" rel="nofollow">П</a><a href="http://electronicmp3.net" rel="nofollow">р</a><a href="http://disco-mp3.com" rel="nofollow">и</a><a href="http://industrial-mp3.com" rel="nofollow">в</a>...</strong> <b><a href="http://eng.country-mp3.com" rel="nofollow">Сп</a><a href="http://eng.electronicmp3.net" rel="nofollow">ас</a><a href="http://eng.disco-mp3.com" rel="nofollow">и</a><a href="http://eng.industrial-mp3.com" rel="nofollow">бо</a>... Прив…

Спасибо…

]]> By: Nicolas Mueggler http://blog.mastertheteam.net/2008/10/share-connectionstrings-between-projects-for-each-developer-differently/comment-page-1/#comment-3 Nicolas Mueggler Mon, 20 Oct 2008 09:26:42 +0000 http://blog.mastertheteam.net/?p=33#comment-3 Originally posted by Salomon Moyal: Dear Nicolas, The aforementioned workaround is great and works quite well with the Sql 2005 and a none service-packed Visual Studio 2008. Another issue came up during the deployment. Our software is a client-server architecured solution. As a result the client makes no direct connection to the DAL. The server-side service is tightly connected to the DAL Tier. The Visual studio vs 2008 server installer is writing the content of the app.config into the ServerProject.config forgettingt the connectionstring.config. You need to go to the installer project and add it manually (right-click: add existing Item move to the solution folder files and link it). The installer will copy it on the target directory. I still got problems writing a clean installer for the database. The databse project itself too is not yet so clean. Conceptually the database installer has no real connection to the Database project. Signed: A customer of mine Sincerly Salomon Originally posted by Salomon Moyal:
Dear Nicolas,

The aforementioned workaround is great and works quite well with the Sql 2005 and a none service-packed Visual Studio 2008.

Another issue came up during the deployment.

Our software is a client-server architecured solution. As a result the client makes no direct connection to the DAL.

The server-side service is tightly connected to the DAL Tier. The Visual studio vs 2008 server installer is writing the content of the app.config into the ServerProject.config forgettingt the connectionstring.config.

You need to go to the installer project and add it manually (right-click: add existing Item move to the solution folder files and link it).

The installer will copy it on the target directory.

I still got problems writing a clean installer for the database. The databse project itself too is not yet so clean. Conceptually the database installer has no real connection to the Database project.

Signed: A customer of mine

Sincerly
Salomon

]]> By: Nicolas Mueggler http://blog.mastertheteam.net/2008/10/share-connectionstrings-between-projects-for-each-developer-differently/comment-page-1/#comment-2 Nicolas Mueggler Mon, 20 Oct 2008 09:25:57 +0000 http://blog.mastertheteam.net/?p=33#comment-2 The described solution is also working for unit tests but you need to edit the *.testrunconfig file. Because the connections.config isn't copied to the out folder of the TestResults structure you need to include it into your deployment. Open the *.testrunconfig by double-clicking in solution explorer and go to the "Deployment" tab. Now you can add the connections.config as additonal file to deploy. The described solution is also working for unit tests but you need to edit the *.testrunconfig file. Because the connections.config isn’t copied to the out folder of the TestResults structure you need to include it into your deployment.

Open the *.testrunconfig by double-clicking in solution explorer and go to the “Deployment” tab. Now you can add the connections.config as additonal file to deploy.

]]>