For me I found the issue was that the slow cheetah property group in the config file was below the section where it checked if it existed. So the fix was simply to move the property group above that line somewhere which would allow the transform to run as expected. Put this: <PropertyGroup Label=”SlowCheetah”> <SlowCheetahToolsPath>$([System.IO.Path]::GetFullPath( … Read more
You can transform Web.config on build. Add this target to *.csproj file: <Import Project=”$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVersion)\WebApplications\Microsoft.WebApplication.targets” /> <Target Name=”BeforeBuild”> <TransformXml Source=”Web.Base.config” Transform=”Web.$(Configuration).config” Destination=”Web.config” /> </Target> Keep the origin configuration in Web.Base.config. It’s enough to enable transformation and it works for any XML config file. SlowCheetah is no longer needed at all. To avoid unwanted transform on publish, … Read more
In my case the error occured while compiling a web project. The folder %userprofile%\AppData\Local\Microsoft\MSBuild\SlowCheetah\v2.5.10.2 was empty. All the SlowCheetah components were in SlowCheetah\v1 folder instead. I’ve copied all files from V1 folder to v2.5.10.2 and everything compiled and transformed fine. To make non web projects compile, I also had to delete V1 folder as suggested … Read more
The Web.config transforms are only applied as part of a publish operation. If you wish this to be done as part of an app.config build operation, then you can use the SlowCheetah – XML Transforms Visual Studio plugin: http://visualstudiogallery.msdn.microsoft.com/69023d00-a4f9-4a34-a6cd-7e854ba318b5
I tried several solutions and here is the simplest I personally found. Dan pointed out in the comments that the original post belongs to Oleg Sych—thanks, Oleg! Here are the instructions: 1. Add an XML file for each configuration to the project. Typically you will have Debug and Release configurations so name your files App.Debug.config … Read more