Feature request: Option to set a custom namespace for the generated output instead of `Windows.Win32`

[MatejKafka]

Currently, I don't see any public way to change the namespace used for the generated C# code. I'm calling CsWin32 manually from PowerShell to access some Win32 APIs and since Add-Type does not allow loading parts of partial classes in separate invocations, running CsWin32 multiple times and loading the resulting C# code with Add-Type results in type collisions. Therefore, I'd like to be able to change the output namespace.

[AArnott]

I sympathize with the desire, but we're not going to deliver on this. We actually used to have this feature and had to remove it because the metadata itself has many namespaces, and combining all of them into one introduces API name conflicts. It also makes emitting code that calls into another generated API far more complicated.
We might revisit this at some point in the future, but at the moment, I want to set expectations that this is not likely to be delivered in the foreseeable future.

[Lamparter]

Is this really impossible?
Almost all generated files begin with namespace Windows.Win32 ("winmdroot") and have additional namespaces appended later, e.g.:

namespace Windows.Win32
{
	namespace Security
	{

Would it be possible to customise the winmdroot namespace?

I'm encountering a very annoying issue where some of my dependencies that have CsWin32 generations (that are set to public) will result in a type conflicting issue if I use CsWin32 in my project.