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.
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?
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.
<?xml version="1.0"?> <!-- For more information on using app.config transformation visit http://go.microsoft.com/fwlink/?LinkId=125889 --> <configuration xmlns:xdt="http://schemas.microsoft.com/XML-Document-Transform"> <appSettings> <add key="Environment" value="Debug" xdt:Transform="Replace" xdt:Locator="Match(key)"/> </appSettings> </configuration>
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="$(...)"/>
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
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".
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
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!
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.
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
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?
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.
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!
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?