Should I always create a Windows Store XAML (instead of a non-XAML) project?

Recently I’ve run into the need to allow the user to enter some text input, which seems to require a MonoGame Windows Store (XAML) Project.

The benefit of using XAML projects is clear, but what’s the downside? Why does MonoGame even offer a non-XAML template? Are there performance downsides? Are there features which are not implemented? Any gotchas I should be aware of?

The only thing I know of is a slight performance hit, but nothing that should affect the game too much.

I run in a huge issue with Monogame Store XAML projects. I just wanted a XAML Monogame project and tought it doesn’t matter if it is for the store. BUT the store apps have security policies which make the use of some external dlls impossible. In my case: Leap Motion.

So be carefull when you use the XAML Store Version.
Btw: I haven’t found a solution for a non store xaml monogame project :confused: