Some simple helper methods that exist in MonoGame being implemented would reduce the friction when using both FNA and MonoGame about fna

[flibitijibibo]

The new methods for MG compat would require EXT per our code standards, so it probably wouldn't help your case much anyway... you're better off writing an MGCompat.cs that does extension methods (and you could probably fit it all in a single file anyway).

As for the Binding allocs, that's in now:

a692d0a

[prime31]

I currently have my own extension methods for this. I was just trying to look out for the rest of the folks using MonoGame who might want to try out FNA.

[flibitijibibo]

It'd probably be good to have someone maintain an MGCompat both for FNA and for XNA; having MG code that uses extensions and is still compatible with XNA will help them with accuracy tests.

[prime31]

I'm all setup to flip-flop back and forth between MG and FNA so ill extract all of the extension methods that I have added into an MGCompat class and keep adding more as I find them. It will at least help out the folks who come accross it in my repo.

[flibitijibibo]

I'd be willing to link to it in the docs as well. This and the MGCB compatibility are probably worth noting...

[prime31]

I'll make a note to document the MGCB setup and link directly to the MGCompat.cs file (once I extract all the extension methods into it) in the FNA setup page here.