Skip to content

Expose new XML namespace for internal types #4031

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
Copilot wants to merge 2 commits into
base: master
Choose a base branch
from
+24 −0
Draft

Expose new XML namespace for internal types #4031

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ee6cb40
Initial plan
Copilot Mar 31, 2026
28fbb4c
Add materialDesignInternal XML namespace and update README documentation
Copilot Mar 31, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,6 +83,25 @@ Install-Package MaterialDesignThemes
[...] >
```

### XML Namespaces

The toolkit exposes two XML namespaces for use in XAML:

| Prefix | URI | Description |
|--------|-----|-------------|
| `materialDesign` | `http://materialdesigninxaml.net/winfx/xaml/themes` | Primary namespace for all public Material Design types, controls, and converters. |
| `materialDesignInternal` | `http://materialdesigninxaml.net/winfx/xaml/themes-internal` | Namespace for types in internal sub-namespaces (`MaterialDesignThemes.Wpf.Internal`, `MaterialDesignThemes.Wpf.Converters.Internal`, `MaterialDesignThemes.Wpf.Behaviors.Internal`). |

> [!WARNING]
> Types exposed via the `materialDesignInternal` namespace are considered **internal implementation details** and are **not guaranteed to maintain backwards-compatibility between versions**. Use them at your own risk.

To use the internal namespace in XAML:

```xml
<Window ...
xmlns:materialDesignInternal="http://materialdesigninxaml.net/winfx/xaml/themes-internal">
```


## Building the source

Expand Down
5 changes: 5 additions & 0 deletions src/MaterialDesignThemes.Wpf/Properties/AssemblyInfo.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,11 @@
[assembly: XmlnsDefinition("http://materialdesigninxaml.net/winfx/xaml/themes", "MaterialDesignThemes.Wpf.Transitions")]
[assembly: XmlnsDefinition("http://materialdesigninxaml.net/winfx/xaml/themes", "MaterialDesignThemes.Wpf.Converters")]

[assembly: XmlnsPrefix("http://materialdesigninxaml.net/winfx/xaml/themes-internal", "materialDesignInternal")]
[assembly: XmlnsDefinition("http://materialdesigninxaml.net/winfx/xaml/themes-internal", "MaterialDesignThemes.Wpf.Internal")]
[assembly: XmlnsDefinition("http://materialdesigninxaml.net/winfx/xaml/themes-internal", "MaterialDesignThemes.Wpf.Converters.Internal")]
[assembly: XmlnsDefinition("http://materialdesigninxaml.net/winfx/xaml/themes-internal", "MaterialDesignThemes.Wpf.Behaviors.Internal")]

// Setting ComVisible to false makes the types in this assembly not visible
// to COM components. If you need to access a type in this assembly from
// COM, set the ComVisible attribute to true on that type.
Expand Down