removed NuGet packages we aren't using right now, because one of them was conflicting with one I need to add
corrected some more NuGet issues before proceeding
set up a simple unit test project and prepared original Nuclex unit tests for import
adding this back in, because it is required by PCLCrypto
got a good chunk of tests running with just some light changes and a couple cheats (::cough:: xnb ::cough::)
since MonoGame doesn't support using the reference renderer, we'll need to use real hardware which we should probably limit to 1 at a time
even with this, and making sure that mockedGraphicsDeviceService specifies Hardware renderer, MonoGame is choking on how to pull off the CreateDevice for OpenGL
switched to DirectX (requires MonoGame >=3.2 installed) to work around the CreateDevice issue in MonoGame, but now it is acting like my (cheatingly attained) XNBs are corrupt
bringing in Nuclex's original fx files, modified to work against DX11 HLSL, which makes more unit tests pass
Wanted to get the vector font unit tests running, even though we can't build XNBs for vector fonts yet. So I used a Nuclex build to make the UnitTestVectorFont.xnb, and then hex edited to point to Nuclectic types. Had to create VectorFontCharacterListReader because ContentTypeReaderManager.LoadAssetReaders was throwing a ContentLoadException ("Could not find ContentTypeReader Type"...) because it currently only supports reading List<T> variations that it either has hard-coded or you inform it of imperatively at runtime.
fixed some more tests
a helper method I'll be needing
ran a ReSharper cleanup so I don't have to fight the formatting anymore
trying to stabilize the tests a bit more, but getting mixed results
Tried to stabilize the tests, but it is a time sink. MonoGame + DirectX + Unit-Tests is just not a good idea right now. Setting the major issues to be skipped.
un-commented more of the original tests
divided a test up to hunt down an issue which has revealed a possible MonoGame bug
verified this is an issue with MonoGame
including more tests in the compile
another healthy round of fixing up unit tests