Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Allow registering xmlns prefixes for foreign assemblies #96
As pointed out in #45, using
[assembly: XmlnsPrefix("http://schemas.dotMorten.com/2018", "custom")] [assembly: XmlnsDefinition("http://schemas.dotMorten.com/2018", "MyClassNamespace")]
only works for assemblies you own.
It would be nice if you could declare those attributes at application level, to provide controls of an assembly with custom namespaces, if they lack those attributes, or even override them.
While the later one isn't essential, i think the first one could be useful, if people share their controls on nuget and don't know about custom namespace prefixes.
At least i've had situations where i was annoyed with the awfully verbose prefixes others chose, or the lack of them alltogether.
Another scenario would be that you are supplied with a viewmodels assembly and are going to use those in your views. Being able to group those namespaces would be neat.
referenced this issue
Dec 6, 2018
The prefixes are only suggestions, and you can always substitute your own at the import site. Being able to add
From: Rob Relyea
Yes, that property is kindof a noop…that we discovered late in the game.
No scenarios have been blocked with the noop.