Configuration Transform


Automatically transform app.config during build process. Once the transformation is set, it will run on other build machines without the extension.

(36) Review
Visual Studio
2013, 2012, 2010
Download (23,327)
E-mail Twitter Digg Facebook
Add to favorites
Reviews (36)
Q and A (37)
Sign in to write a review
Sort by:

by Idsa | January 27 2015

by reddykkk | January 15 2015

by alemos | December 24 2014

This has been an awesome timesaver. I commend you on your efforts. Thank you for this extension.

I created a base app.config file and then my environment-based files with only the values that needed changes. The result is perfect, when compiling, the correct file is generated so we can test without commenting and commenting values in each environment.

I think this should be in the next release of Visual Studio.

by JCP-Displayname | November 13 2014

I added a web reference to the project and the Hierarchy of config files went flat and the transforms stopped working. Now the when you click on add config transforms you get a message no changes were made.
Also it is now transforming for the wrong configuration, it is stuck on production.
Also I can no longer view any transformations
Using VS 2010
Is there a fix or workaround for this?

by Hernan Veiras | November 10 2014

Awesome extension!

by Pablo Castilla | November 06 2014

Looks good, but I am not able to add a transform link in VS2013. I want to share the transformation between projects

Is it possible? Can you tell me the steps to do it?

Golan Avraham November 07 2014
| Edit |

it has noting to do with the extension
It's very simple
To create a link to an existing item:
In Solution Explorer, select the target project.
On the Project menu, select Add Existing Item.
In the Add Existing Item dialog box, locate and select the project item you want to link.
From the Open button drop-down list, select Add As Link.

See Linked Configs Step by Step Instructions

by mindriven | October 14 2014

by tanaka_733 | October 09 2014

This is a great tool!
It is useful because configuration transform by this extension does not depend this extension itself because it edits csproj file.

It is more better to improve config preview because preview result does not contain line break.

by Mike Calvin | October 09 2014

Works Great. I was able to add app.config transformations and preview them in less than 5 min. Perfect.

by gord888 | September 15 2014

Works great - just needs a "preview transform" functionality that web.configs have.

Golan Avraham September 28 2014
| Edit |

version 2.0 released with preview support

by IanBusko | August 29 2014

This solution fills a huge hole in Visual Studio. It's easy to setup and (for me) has done its job perfectly so far. This makes setting up test stages much easier.

by darylnight | August 06 2014


by xuzf | July 20 2014

It solved my headache, thanks very much!

by SteveKo | July 17 2014

Great plugin. Works like a charm. Just need to read instructions properly ! :)

by Real Daniel Byrne | June 29 2014

Doesn't work at all. Added a simple flag per the example on the download page.

Environment = ""
and Environment = "Debug" for Debug release. I then test for this flag in code.

if (ConfigurationManager.AppSettings["Environment"] == "Debug")

The debugger clearly shows that ConfigurationManager.AppSettings["Environment"] == "" and not "Debug".


Golan Avraham July 17 2014
| Edit |

what about?

<?xml version="1.0"?>
<!-- For more information on using app.config transformation visit -->
<configuration xmlns:xdt="">
<add key="Environment" value="Debug" xdt:Transform="Replace" xdt:Locator="Match(key)"/>

please follow instructions and see if it works

by RealeXavera | June 19 2014

by Rodrigost | May 31 2014

Great job!
It helped a lot and let me give up wasting my time solving issues regard about config files in Windows Services projects.

by SegaWang | April 26 2014

Super nice tool. Thanks a lot

by Oleksiy Mishchenko | April 18 2014

Great little tool!
Easy to install and use.
Works well as expected.


by El Bruno | March 30 2014

Amazing app! I used it a lot!

1 - 20 of 36 Items   
Sign in to start a discussion

  • Is the source code of this extension available somewhere?
    2 Posts | Last post February 20, 2015
    • Will consider contributing a feature that we need...
    • Trying to re-launch discussion... 
      Is the source code of this extension available somewhere?
  • Is it possible to change the path to Microsoft.Web.Publishing.Tasks.dll?
    1 Posts | Last post February 06, 2015
    • It works well on our local dev boxes but fails to find Microsoft.Web.Publishing.Tasks.dll assembly on our build servers which may not have Visual Studio installed or that assembly is located in another location.
      That might be solved by having that assembly in our solution folder and changing the path in this line: 
      <UsingTask TaskName="TransformXml" AssemblyFile="$(...)"/>
  • Doesn't work for Web projects
    4 Posts | Last post February 04, 2015
    • I've applied transformation to a web.config and it changed the web.config placed in bin folder but it seems like what really matters is the web.config placed in the root folder (but it is not changed). Am I doing anything wrong or this scenario is not supposed to work?
    • this extension doesn't support web.config
      web.config has a built-in capability to transform config
      you don't need this extension for web.config
    • But as I know built-in capability works only during the publish process. I hoped to use your plugin to make web.config be updated on a build basis
    • Same issue here, I need to produce an MSI installer from a Web Setup Project. 
      Anyone successfully done that without using Wix?
  • Error
    1 Posts | Last post January 29, 2015
    • I have this working for one of my projects no problem, the other is proving problematic it seems to be trying to pass in the the name CareManager.vbproj.App.Config for some reason, any ideas?
      "obj\Debug\CareManager.vbproj.App.config;obj\Debug\CareManager.exe.config" is an invalid value for the "ConfigFile" parameter of the "GenerateApplicationManifest" task. Multiple items cannot be passed into a parameter of type "Microsoft.Build.Framework.ITaskItem".	
  • VS 2013 Update 4
    2 Posts | Last post January 23, 2015
    • I have tested the extension with VS 2013 Update 4
      All works preview/transform/linked transform
      Make sure you read the instructions especially when using linked config
      Demo solution:!139&authkey=!AE6qGnmd99lwsdg&ithint=folder%2c
    • I'm testing out version 2.1 with VS 2013 Update 4 and I get the "different computed hash than specified in manifest" error when we try to install the app using ClickOnce.
      This is the same error that bluebunny was receiving in his post below.  We are currently using VS 2012 Update 4 and version 1.4 of your tool and that works fine.  I'm hesitant to update to 2.1 in case it breaks as well in VS 2012.
      Any ideas on how we can resolve this issue in VS 2013?  We'd like to upgrade but I won't do it if we can't use your fantastic tool.  It is possible to put version 1.4 out somewhere for download so I can try that in VS 2013?  Thanks!
  • transform during the deployment issue
    1 Posts | Last post January 05, 2015
    • I have a "WCF Class library" project in VS2013 update 4, and while I was able to setup, configure and preview all transforms inside VS, they do not work when deployed to the target IIS server. It deploys the base app.config only without any transforms. Please advise. Thanks.
  • VS 2013 & 2012 Update 4 problem
    1 Posts | Last post December 19, 2014
    • Just to report - this extension stopped working when I installed Update 4 for VS2013 and VS2012. Preview transform is working, but app.config is not transformed on build action.
      Still cant figure out why M$ wont make config transform work outside web projects
  • Preview with no transform
    3 Posts | Last post December 16, 2014
    • I am having issue where I can preview app.config transforms, but the transform does not output to the build folder. Instead I get the unaltered top level app.config. 
      Am I missing something obvious here? 
    • I am using vs2013 sp4
    • The obvious thing that I was missing was that the app.config gets renamed. I was actually looking for app.config instead of <dll name>.config. 
  • Click Once - different computed hash than specified in manifest
    6 Posts | Last post December 04, 2014
    • We've updated to v2.1 recently.  Ever since updating I can no longer deploy ClickOnce apps.
      I just tested again with absolute most basic settings, still gets the error when deployed.
      This is with VS 2013 Update 4.
      Do you have the prior version available to downgrade to while this is investigated? I really did not want to have to switch back to SlowChetah again.  It was borked for so long last year it was killing our productivity.
    • sure, just give me drop location and requested version
    • Can you share the install for v1.4 with me via OneDrive or DropBox?  User name for both: greg_burns at hotmail
      Or even google drive if you prefer: bluebunny72 at google
      Let me know if I can help with troubleshooting this issue in anyway.
      With SlowCheetah going away, this extension is our last hope until MS gets their act together and finally adds it to VS natively.
      Thanks a ton!
    • Got it. Thanks so much!
    • We've been doing more testing here. It appears to be VS 2013 Update 4 that maybe the issue. Both your v1.4 and v2.1 work in VS 2012 Update 3/4 and VS 2014 Update 2/3, but not 4.
      Have you tested in VS 2013 Update 4?
    • not yet
      thanks for the update
  • Setup installer
    1 Posts | Last post November 21, 2014
    • I finally got this to work with a simple application. 
      I then added an installer project to my solution but it will only package up the main app.config rather the transformed config file.
1 - 10 of 37 Items