Doesn't work with any VB project types. The fix is to remove the <DependentUpon>app.config</DependentUpon> tags in your project file. You won't get the nice nesting, but all the files will at least show up and transform.
The plugin works great in Visual Studio 2013. The big win with this plugin is that the underlying transformation engine is a part of Visual Studio so once the configuration is in place the plugin is not needed for the solution to build.
This works nicely in previous for me, but now i have a new requirement. I need to update the string value on the basis of Build agent. For example i have transformed the path using config transformation. <sessionFactory name="quotek" factoryConfigPath="c:\Builds\1\App.nhibernate.config" xdt:Transform="Replace" xdt:Locator="Match(name)" /> Here 1 is the build agent, previously i only have the 1 build agent so i have added the above path for transformation.Now i have 4-5 build agent, and my App.nhibernate.config file exists under the build agent folder.
How can we dynamically update this path on the basis of Build agent.
This extension doesn't work with any VB project types. The fix is to remove the <DependentUpon>app.config</DependentUpon> tags in your project file. You won't get the nice nesting, but all the files will at least show up and transform.
You should not do this. This is a result of a "By Design" behavior in Visual Basic. If you want to see the config transforms use the following steps:
1. Go to the Solution Explorer.
2. Click on the Project.
3. Click the icon that looks like multiple pages in the Solution Explorer tool bar. (The tool tip will read Show All Files.)
4. Expand by clicking the arrow next to App.config.
Configs nested in folders do not work out of the box. I updated the .csproj file to include a MakeDir task, so that the necessary out put folder is created before the transform task kicks off. Also updated the Source/Destination/Transform paths to include the folder structure. The preview feature is nice, but you'll run into a few issues if you are using nested folders. If you are using configs nested in folders I would recommend using the msbuild tasks, or wrapping the transforms in powershell. I've used the article below for doing transforms on config files in our CI builds in visual studio online.
We have a project which was built in VS2012, and needs to stay in 2012 due to the CRM Sdk, but we keep getting the version 12.0 dependency error. Is version 2.1 available anywhere, as we'd really like to use this product.
Thanks for your contribution, Golan, but I'm wary of using any extension that isn't open source. If it suddenly breaks on a VS upgrade, I want to be able to quickly fix and move on, not switch horses altogether to move on.
I have this in config:
<level value="ALL" />
I need this in Debug config:
<level value="ALL" />
What transformation statements should I include and where?
I setup appSettings.config and log4net.config in my project with your extension. I built the application and only one of the *.config files. I looked at the .csproj file and noticed the extension created a separate <Target name="AfterBuild"> for appSettings.config and log4net.config. This won't work because MSBuild will only use the last one in the project file. I had to modify the project file to look like this:
<!--Generate transformed config in the output directory-->
<TransformXml Source="appSettings.config" Destination="$(OutputPath)appSettings.config" Transform="appSettings.$(Configuration).config" />
<TransformXml Source="log4net.config" Destination="$(OutputPath)log4net.config" Transform="log4net.$(Configuration).config" />