Flexible TreeView

Flexible TreeView screenshots 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!



With Flexible TreeView you will:

  • Concentrate only on your application development.
  • Shorter release time.
  • Make your development process as smooth and easy as possible.
  • Make the style of your application unforgettable.
resulting in lower total cost, faster time to market and increased customer satisfaction.


File Content Transformer

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!


File Content Transformer save your time when you need:

  • Alter or transform text file (a source code file, xml file or any other text file) to another format.
    For example, you are selling source codes that contain entire files, blocks of code or comments that should be altered or deleted before being sent to the client.
  • Clean source codes of the supporting text, comments, non-public text, etc.
  • Insert text of the license into the file header under which it is distributed.
  • Check if the files or directories do not contain or, oppositely, do contain predefined text of block of text.
  • From variety of files you have to delete those that contain definite block of text.


Project Config Transformer

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.


Main benefits of using Project Config Transformer:

  • You don`t have to deal with tons of transformed config files (with almost the same content) and issues when web.config file was not auto-published when you debug your web application in Visual Studio locally.
    You work with only one config file`s template that has nothing but your application`s configuration.
  • You don't need to specifically and intricately encode an original template, from which an output file will be generated.
    Just copy into the template how the file should look like once finished, then add data placeholders where specific values for the final environment are to be added.
  • Clear and simple format of the file with values of variables for insertion.
    The file with values for insertion is a general text file of PropertyName=PropertyValue format, what frees you from work with XML, DOC, XLS, etc. files that sometimes demand additional expensive software to be installed.
  • One .config file is shared among many build configurations, separate projects or even solutions. You don`t need to duplicate any piece of your configuration anymore.
  • Easy integration into existing build process.
    Project Config Transformer supports integration with MSBuild, Visual Studio or any other. Also it doesn't demand additional software.
  • Easy integration with source control systems.
    Since a file with values for insertion is an usual text file, you can add it into source control system and easily track changes in it.
  • Auto-transforms web.config when locally debugging a web application in Visual Studio under Cassini or IIS.
  • Support parameters grouping and inheritance, what makes it easier to work with them. Parameter values for the insertion may be grouped by build-configurations' names, for example. With inheritance you can set default values for all or some parameters and override values of the parameters, different from default parameters, in another group.
  • Value of a parameter may depend on value of another parameter.
    Any parameter can fully or partially consist of values of other parameters, allowing the user to determine parameter value without data duplication.