slowcheetah

I am trying to transform all of the web.config files in a project I have, here's a my tree structure: Transform.bat Transforms ConfigTransform.proj Web.Transform.config Website web.config Views web.config There's more web.config files, but the idea is that this will find all of them and apply the same config transform on them. I've taken a few hints from a blog post I found but I get stuck in the last step, the actual transformation. Also there's a bit of a rough part in the middle that I don't really like (I don't quite understand what I'm doing and I'm obviously doing it wrong). Here's where

I have setup some configuration transforms in my web.config for my connectionStrings, etc. But I have separated out some areas of my web.config into separate files, ex) appSettings.config. How can I configure Visual Studio and MSBuild to perform config transformations on these additional config files? I have already followed the approach of the web.config to relate the files together within my web application project file, but transformations are not automatically applied. <ItemGroup> <Content Include="appSettings.Debug.config"> <DependentUpon>appSettings.config</DependentUpon> </Content> <

I have a project I am trying to use SlowCheetah for. I have created my config file (Test.web.config) and all the transformations I want to use (Debug_Mock.config, Debug_SQL.config, Release) in my Build configuration I have a post-build event is supposed to copy the transformed file into another directory but the file cannot be found (error xcopy exited with code 4) SlowCheetah doesn't seem to be transforming the file and placing it in the output directory (bin folder) like I would expect. Does anyone have any ideas as to why it is not happening, maybe a setting somewhere? FYI: This process

After installing Slow Cheeath (v. 2.5.10.3) to two projects in my solution, I am receiving the following error: "The "SlowCheetah.Xdt.TransformXml" task could not be loaded from the assembly C:\Users \User\AppData\Local\Microsoft\MSBuild\SlowCheetah\v2.5.10.2\SlowCheetah.Xdt.dll. Could not load file or assembly 'file:///C:\Users\User\AppData\Local\Microsoft\MSBuild \SlowCheetah\v2.5.10.2\SlowCheetah.Xdt.dll' or one of its dependencies. The system cannot find the file specified. Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and

I installed the SlowCheetah package via nuget and added transform files for my web.config based on Build config. However, on building, the web.config does not get transformed. I checked my project file and did see entries for SlowCheetah PropertyGroup and Import elements. I dont see a target for transformation in the project file. If I add an app.config, the app.config file does get transformed. It is my understanding that installing the SlowCheetah package should automatically add the web.config transform target to the MSBuild file for the project. I can add it manually but I thought

I’m a fan of the new VS 2010 Web.config transformations. I use this feature for deployment purposes and wondered if it is possible to use them for debugging too. I think of using them in the IDE: I want to create different built configuration (with linked transformation configurations); choose one of them; start the web site in the IDE and debug the different configurations this way. Update Thanks to a 3rd party plugin, SlowCheetah , this is now possible. Scot Hanselman has a blog post about it. Original response: Unfortunately, the web.config transformations appear to effect only publishing

I have a main Web.config file, and under that there is a Web.Test.config , Web.Development.Config etc. When I preview the transformation via SlowCheetah on the Test config, it appears to transform the values correctly. When I switch my build environment from Development to Testing and try to debug the application, the application runs under whatever values are in the main Web.config file (i.e. it is not transforming anything). How do I make the build environment pick the correct config when debugging rather than just always using the base Web.config file? Is this possible? You can transform