Can NativeMethods.txt be split into two files? Or can the two scenarios for allowMarshaling be listed?

[sgf]

if split into two files:
One file would be: NativeMethods.txt with "allowMarshaling": true (default)
The other would be: NativeMethods.NoMarshaling.txt with "allowMarshaling": false

Of course, it would be excellent if CSWin32 could list both scenarios.

Because simply enabling or disabling it would obviously cause the application to lose many conveniences.
For example, when we need to wrap COM ourselves, we need "allowMarshaling": false.
However, when we need automatic handling, such as the callback function for PInvoke.EnumWindows, using a simple delegate is obviously more convenient.

[jevansaks]

I recently added support to collect all AdditionaFiles which end with NativeMethods.txt. So you can have "Foo.NativeMethods.txt" and "Bar.NativeMethods.txt" now: #1550.

The other part of your post seems to ask for mixing allowMarshaling:true and allowMarshaling:false in the same project. This is not supported.

[sgf]

I know it's not supported, which is why I brought it up. I'm currently using two projects to achieve this.