marazt/config-transformation

A Visual Studio extension which enables ability to transform various config file even there does not exist build definition for the transformation file. Supports all .NET projects even WebSites.

Config Transformation Visual Studio Extension

Version 1.5.0.0

Author marazt

Copyright marazt

License The MIT License (MIT)

Last updated 24 March 2019

Visual Studio Gallery Link

About

This extension enables ability to transform various config file even there does not exist build definition for the transformation file.
For example, if you have multiple configuration transformations, e.g., web.Debug.config, web.Release.config, web.UAT1.config, web.UAT2.config, web.UAT3.config, web.Production1.config, web.Production2.config. And you want switch between these configuration while developing without changing actual build definition or editing the web.config manually.

Abilities

• Generate configuration transformation while developing.
• Preview transformation result.
• Application output (transformation progress, errors, infomation) in General Output window.
• Configuration in Tools -> Options -> Config transformation menu.
• Transformation file nesting, can be set in Tools -> Options -> Config transformation menu.
• Supports Visual Studio 2012, Visual Studio 2013, Visual Studio 2015, Visual Studio 2017.

How To Use It

• File you want to change must be checked out (not locked, not readonly).
• Click on the transformation configuration you want to run with the right mouse button and click "Execute transformation" option.

• Extension options can be found in Tools -> Options -> Config Transformation

• Information about transformation can be found in General Output Window.
• You can see the transformation preview by Preview transformation menu item.

TODO

• Unit tests - because the project was a long time private and written very fast for internal purposes, no tests were written, although they should :/.

Versions

Version 1.5.0.0 - 2019/03/24 Support for VS2019

• Support for VS2019. Thanks @tbertenshaw for PR.

Version 1.4.0.0 - 2018/02/08 Support for VS2017

• Support for VS2017. Thanks @tbertenshaw for PR.

Version 1.3.7.0 - 2016/04/09 (Added to GitHub)

• New option item Write attributes on a separate line added. If this option is set to true, transformed config has every attribute on separate line. Default value is false.

Version 1.3.6.0 - 2015/09/12

• Removement of the .NET 4.5 dependency which caused that it was not possible to install the extension although the framework was correctly installed.

Version 1.3.5.0 - 2015/09/12

• Change of the temporary config file to ".config" instead of ".tmp" to enable syntax coloring.

Version 1.3.4.0 - 2015/08/04

• Added support for Viasu Studio 2015.

Version 1.3.3.0 - 2014/09/23

• Bug fix: Added information message about readonly file which should set to readwrite or checked-out.

Version 1.3.2.0 - 2014/07/30

• Added transformation files nesting option.

Version 1.3.1.1 - 2014/07/20

• Bug fix

Version 1.3.1.0 - 2014/07/17

• Added Preview transformation ability.

Version 1.3.0.0 - 2014/07/16

• Added logging to General Output Window.

Version 1.2.0.0 - 2014/07/16

• Added options menu to set extension configuration in Tools -> Options -> Config Transformation.

config-transformation's Issues

Support for Visual Studio 2017

Hey,

Would you have time to add support for Visual Studio 2017.

Cheers.

Support for newer Visual Studio versions

As of today, the extension is supported upto VS2019. Can this be extended for newer versions too?

Installation

Hi,

the extension cannot be installed in Visual Studio 2019 Professional.
I can only select Visual Studio 2017 Professional!

Can you please correct that?

Thank you!

Config file name with multiple dots fails

I noticed that if you call the config file using multiple dots it fails to preview and apply the transformation.

Working file names
Web.ANYSTRING.config
App.ANYSTRING.config

Not working
Web.name.surname.config
App.any.string.config

Expected behaviour
Should not matter how many dots are in the file name.

Update extension to support asynchronous autoloading

Update extension to support asynchronous autoloading.

https://docs.microsoft.com/en-us/visualstudio/extensibility/synchronously-autoloaded-extensions?view=vs-2019

Auto-generated integrations tests fail

Tests generated by VS automatically are failing. Original project was created for VS2012 (which I don't have installed), tests have been run on VS2015.
There is similar issue on SO - http://stackoverflow.com/questions/31329613/visual-studio-package-integration-tests-failing. Not solved for a very long time :/

EDIT1: Similar issue was reported to MS

• https://connect.microsoft.com/VisualStudio/feedback/details/756416/vs-2012
• Workaround for VS2012 does not work for VS2015 (testsettings are obsolete)
• Issue is closed with status "Won't fix"

1.5.1.0 Won't install on VS2019

The 1.5.1.0 version prompts only Visual Studio 2017 not 2019 when installing.
Also in the readme there is not 1.5.1.0 version mentioned.