LocBaml/BamlLocalizer for WPF on .NET Core

Taken from the original LocBaml and mostly rewritten

Preface

---

• This is an updated version of the LocBaml tool, originally taken from Microsoft WPF Samples
• Tested with resources using both ResourceReader and DeserializingResourceReader
• Currently the expected input is a satellite resource assembly with generated .resources stream
• Base information can be found on MSDN but I'd for recommend doing x:uid manually
• Currently only CLI variant is available but I plan to create a simple GUI editor as well
• The assemblies are currently loaded in AssemblyLoadContext.Default, this is required for BamlReader

Usage (Parsing neutral assembly)

• Put LocBamlCore files into the main executable folder (e.g. Debug/Release) folders
• Use the following command-line arguments to generate the translations file:
• /parse en-US\WpfAppDemo.resources.dll /out:ExtractUIDs.csv /verbose
• In most cases, your BAML streams depend on controls/types outside standard WPF assemblies
• Therefore, pass paths to those assemblies using /asmpath:WpfAppDemo.dll arguments

Usage (Generating localized assembly)

• Put LocBamlCore files into the main executable folder (e.g. Debug/Release) folders
• Use the following command-line arguments to generate the satellite assembly:
• /generate en-US\WpfAppDemo.resources.dll /translation:ExtractUIDs.csv /culture:no-NO /out:no-NO /verbose
• In most cases, your BAML streams depend on controls/types outside standard WPF assemblies
• Therefore, pass paths to those assemblies using /asmpath:WpfAppDemo.dll arguments
• Note: The output directory should be currently created manually beforehand

Issues

• In case you encounter any issues, please create one in LocBamlCore - GitHub issues
• Do include a proper description and reproduction project/files in case you're creating one

PRs

• Before creating a PR, please start an issue explaining what is it you want to fix/improve