Wanted to let you know that I just released v2.3 of my Visual Studio extension SlowCheetah. If you are not familiar with SlowCheetah here is an intro. For client projects (i.e. non-web projects) it allows you to transform the app.config (or any XML file) on F5 (debug) or CTRL + F5, it also has a preview functionality which allows you to see the results of the transform quickly. For Web Projects it allows you to transform XML files during package/publish (and of course the preview functionality works in web projects too). The transform behavior is all in MSBuild targets/tasks so command line support is built in. It’s also easy to integrate SlowCheetah into CI servers.
Below are the updates that we have in v2.3.
Preview support in VS 11
In the previous version we added support for VS 11 but the preview functionality didn’t work because the preview tool we used in VS 2010 didn’t exist in VS 11. VS 11 now has a new diffing tool and in this version we now support invoking this new service.
ClickOnce related updates
ClickOnce support was added in a previous version but the support was limited to app.config. In this version when you publish an application using ClickOnce if you have transforms in any other XML file defined those transforms will be applied and published.
Setup projects updates
Similar to ClickOnce the support for setup projects was limited to app.config only. In this version we now have support for all XML files not just app.config. There was also a bug in the previous version relating to setup projects. For setup projects if a file was being transformed from a linked file when you built the solution you would receive an error. We have fixed that bug.
Sayed Ibrahim Hashimi @SayedIHashimi
I asked this question in the Q&A in the project gallery, but thought I would repeat the question on this blog.
I had no problems installing the SlowCheetah extension or seeing it working in VS 2010.
That being said, I was looking into how to remove this extension and couldn't find SlowCheetah registered in the Add-In Manager in the IDE or in the usual locations for VS 2010 extensions.
See the link in MSDN Library where it explains where the Installation location is for vsix packages.
http://msdn.microsoft.com/en-us/library/ff363239.aspx
****
Installation Location
During installation, Extension Manager uncompresses the .vsix file and puts its contents in %LocalAppData%\Microsoft\VisualStudio\10.0\Extensions\Company\Product\Version\. Company, Product, and Version are specified in the extension.vsixmanifest file, and correspond to the namespace, project name, and version number that are set in the project properties.
By default, the installation applies only to the current user, because %LocalAppData% is a user-specific directory. However, if you set the AllUsers element of the manifest to True, the extension will be installed in ..\Visual Studio installation folder\Common7\IDE\Extensions\Company\Product\Version\, and will be available to all users of the system.
*****
So, if any of the developers in my team using this extension has any problems with it, how do they remove it?
Thanks in advance,
LizetP
Comments are closed.