MyNet.Xaml.Merger.MSBuild 2.0.1

dotnet add package MyNet.Xaml.Merger.MSBuild --version 2.0.1

NuGet\Install-Package MyNet.Xaml.Merger.MSBuild -Version 2.0.1

This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.

<PackageReference Include="MyNet.Xaml.Merger.MSBuild" Version="2.0.1" />

For projects that support PackageReference, copy this XML node into the project file to reference the package.

paket add MyNet.Xaml.Merger.MSBuild --version 2.0.1

The NuGet Team does not provide support for this client. Please contact its maintainers for support.

#r "nuget: MyNet.Xaml.Merger.MSBuild, 2.0.1"

#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.

// Install MyNet.Xaml.Merger.MSBuild as a Cake Addin
#addin nuget:?package=MyNet.Xaml.Merger.MSBuild&version=2.0.1

// Install MyNet.Xaml.Merger.MSBuild as a Cake Tool
#tool nuget:?package=MyNet.Xaml.Merger.MSBuild&version=2.0.1

The NuGet Team does not provide support for this client. Please contact its maintainers for support.

<p align="center"> 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 MyNet.Xaml.Merger or the MSBuild version MyNet.Xaml.Merger.MSBuild to make use of the provided functionalities. </p>

</div>

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

<XAMLCombineItems Include="Themes/Controls/*.xaml">
  <TargetFile>Themes/Generic.xaml</TargetFile>
</XAMLCombineItems>

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:

<PropertyGroup Condition="'$(IsBuildingInsideRider)' == 'True'">
  <DefaultItemExcludes>$(DefaultItemExcludes);Themes\Controls\*.xaml</DefaultItemExcludes>
</PropertyGroup>

<ItemGroup Condition="'$(IsBuildingInsideRider)' == 'True'">
  <Page Include="Themes\Controls\*.xaml" />
</ItemGroup>

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 and template files.

Using the MSBuild-Task

<XAMLColorSchemeGeneratorItems Include="Themes\ColorScheme.Template.xaml">
  <ParametersFile>Themes\GeneratorParameters.json</ParametersFile>
  <OutputPath>Themes\ColorSchemes</OutputPath>
</XAMLColorSchemeGeneratorItems>