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>
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!
My previous testing seemed to suggest VS 2012 Update 4 would work with version 2.1 (for ClickOnce). (Take an system image backup before applying in case it does not!)
Sadly VS 2013 Update 4 does not work with version 2.1 (for ClickOnce).
This post from the VS Team has given my hope that the SlowCheetah will be updated and fully supported by VS 2015.
Golan, I downloaded you demo solution. It does indeed work with VS 2013 Update 4 as a click once deployment! Which got me wondering what is different about my projects. The obvious difference was mine are all Visual Basic not C#.
Please download my demo and attempt a click once deployment. You should experience the "different computed hash than specified in manifest" error.
Hopefully this leads to a fix. Would love for this to be working again with VS 2013 Update 4.
Forgot to mention I'm using VB.NET as well.
Disappointed to say that reverting back to version 1.4 didn't work for me; my ClickOnce install is still broken in the same way as with 2.1:
* Activation of C:\Users\***\PD-CLU.appref-ms| resulted in exception. Following failure messages were detected:
+ File, PD-CLU.exe.config, has a different computed hash than specified in manifest.
Come on, Golan - people love this thing, if you could just fix it!
I've tried adding this to existing projects, followed instructions, and transforms don't work. I can add a new config transforms and see previews, but when I build/rebuild solution, no transformations are applied to App.config.
I've even downloaded the sample app from the description and that too does not work. I have the same problem with SlowCheetah. Any idea what the problem could be?
Hi i have used the config transformation for test project in VS2013 and on building, the conifg file is getting transformed to the corresponding build environment(ex:Test).
But when i do publish the same the WCF project using VS2013, the published web.config is not getting transformed. Please advise.
This is a gem no doubt! I have one tiny little nuance I'd like to discuss. If I create a new profile, and lets say i call it "New Debug". I noticed that after applying a transformation that it modifies my Output Path in Build Properties to "bin\New Debug". I have numerous scripts tied to post build events, and I really don't want to change the output path ever, regardless of the profile I choose to build. I know it's easy to go and change it back that one time and it sticks forever, but is there a way to suppress the modification to the application output property on the initial?
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".
Hello, this is a great tool!
I have a problem when I need to transform my nlog.config as well as app.config in my application. The tool helps me to add two Targets in csproj but only the nlog.config transformation is working, not both.
Am I missing something here? Does the extension support multiple config file transformation? Thanks.
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="$(...)"/>