https://github.com/batzen/xamltools

https://github.com/batzen/xamltools

cli hacktoberfest msbuild wpf

Last synced: 10 days ago
JSON representation

• Host: GitHub
• URL: https://github.com/batzen/xamltools
• Owner: batzen
• License: mit
• Created: 2021-12-29T10:13:31.000Z (almost 3 years ago)
• Default Branch: develop
• Last Pushed: 2024-07-13T07:58:06.000Z (4 months ago)
• Last Synced: 2024-10-11T14:29:41.245Z (25 days ago)
• Topics: cli, hacktoberfest, msbuild, wpf
• Language: C#
• Homepage:
• Size: 270 KB
• Stars: 36
• Watchers: 3
• Forks: 4
• Open Issues: 7
• Metadata Files:
  • Readme: README.md
  • Changelog: Changelog.md
  • Funding: .github/FUNDING.yml
  • License: LICENSE

Awesome Lists containing this project

README

        
# XAMLTools

[![Build status](https://img.shields.io/appveyor/ci/batzen/XAMLTools.svg?style=flat-square)](https://ci.appveyor.com/project/batzen/XAMLTools)

[![Release](https://img.shields.io/github/release/batzen/XAMLTools.svg?style=flat-square)](https://github.com/batzen/XAMLTools/releases/latest)

[![Issues](https://img.shields.io/github/issues/batzen/XAMLTools.svg?style=flat-square)](https://github.com/batzen/XAMLTools/issues)

[![Downloads](https://img.shields.io/nuget/dt/XAMLTools.MSBuild.svg?style=flat-square)](http://www.nuget.org/packages/XAMLTools.MSBuild/)

[![Nuget](https://img.shields.io/nuget/vpre/XAMLTools.MSBuild.svg?style=flat-square)](http://nuget.org/packages/XAMLTools.MSBuild)

[![License](https://img.shields.io/badge/license-MIT-blue.svg?style=flat-square)](https://github.com/batzen/XAMLTools/blob/master/License.txt)

Various tools for easing the development of XAML related applications.

As i only use WPF myself everything is focused on WPF, but things should work for other XAML dialects (at least in theory).

You can either use the commandline tool `XAMLTools` or the MSBuild version `XAMLTools.MSBuild` to make use of the provided functionalities.

CI builds can be consumed from [appveyor](https://ci.appveyor.com/nuget/xamltools).

## XAMLCombine

Combines multiple XAML files to one large file.  

This is useful when you want to provide one `Generic.xaml` instead of multiple small XAML files.  

Using one large XAML file not only makes it easier to consume, but can also drastically improving loading performance.

### Using the MSBuild-Task

```

  Themes/Generic.xaml

```

The MSBuild-Task includes the items used for combining as pages during debug builds and removes them from pages during release builds.

This is done to reduce the binary size for release builds and still enable intellisense in debug builds for those XAML files.

**Remarks when using Rider**  

To get intellisense in debug builds inside the XAML files and to prevent duplicate display of those files you have to define:

```

  $(DefaultItemExcludes);Themes\Controls\*.xaml

  

```

### Using the executable

`XAMLTools` accepts the following commandline parameters for the `combine` verb:

- `-s "Path_To_Your_SourceFile"` => A file containing a new line separated list of files to combine (lines starting with # are skipped)

- `-t "Path_To_Your_Target_File.xaml"`

## XAMLColorSchemeGenerator

Generates color scheme XAML files while replacing certain parts of a template file.

For an example on how this tool works see the [generator input](src/XAMLTools.Core/XAMLColorSchemeGenerator/GeneratorParameters.json) and [template](src/XAMLTools.Core/XAMLColorSchemeGenerator/ColorScheme.Template.xaml) files.

### Using the MSBuild-Task

```

  Themes\GeneratorParameters.json

  Themes\ColorSchemes

```

### Using the executable

`XAMLTools` accepts the following commandline parameters for the `colorscheme` verb:

- `-p "Path_To_Your_GeneratorParameters.json"`

- `-t "Path_To_Your_ColorScheme.Template.xaml"`

- `-o "Path_To_Your_Output_Folder"`