Can Web.config Transformation process impact on all solution's projects?
<p>I'd like to understand if what I have in my mind is a "good practice" and if so, how I can get it.</p>

<p>First of all let's say that we are using VS 2010 and the .Net 4.0.</p>

<p>In our solution we have one ASP.NET WEB Application and other Class Library projects, where some of them are referenced in the WEB Application project.</p>

<p>For the WEB Application we've implemented the "Web.config Transformation" since we manage the deploying on three different environments (Test, UAT, and Production).</p>

<p>The point is this, as I said we have projects referenced in the WEB App. and some of them access to the database, so the question is this: is there a chance to let the WEB.config transformation process to impact on those projects in terms of the connection string? Basically  before we deploy, once we select the environment (i.e Test), we'd like that choice will affect to the app.config files of the referenced projects.</p>
