Flexible TreeView is our proven state-of-the-art TreeView-ListView-Grid hybrid control for Microsoft .NET WinForms and WPF that composes unmatched flexibility and performance.
When we are talking about unmatched flexibility we mean that you can implement almost any your requirement using Flexible TreeView.
It provides dozen of features that none of the similar products on the market does have!
File Content Transformer allows to change (replace, delete or add) the entire content of the text file (source code on any programming language, xml, plain text, etc.) or its separate blocks defined by the block`s template. With that using the transformation script the user defines the algorithm and sequence of the file transformation.
When searching for a block of text which is to be changed, File Content Transformer allows to specify many parameters of such a block, what allows you to find and transform a text block of any complexity.
With this File Content Transformer can be easily integrated into existing build system (MSBuild, Visual Studio, etc.), any continuous integration system or any other system that is able to run external programs.
Last but not least is that File Content Transformer can be deployed by simply copying the files to your build computer and it isn't dependent on the additional software.
File Content Transformer greatly saves your time when mass processing of text files!
Have you ever had a problem when project file content (for example web.config file or file with settings) or solution depends on the selected build configuration or the environment this project is compiled for?
Or are there many build configurations in the solution so that supporting big configuration files for each build configuration turns into a daunting manual routine that always has a risk of bugs?
Project Config Transformer will help you solve this problem quickly, efficiently and safely!
It allows to insert predefined values of variables in specific positions of a text file. With this all values of variables are stored in a separate file and they form groups (as build configuration name, target environment name, etc.) to be easily analyzed or edited.
This frees the developers from creating and supporting multiple copies of one and the same file (for example, web.config file) with minor differences specific for the final environment.