The MonoGame 3.8 release marks some big changes in how we build and distribute.
Refer to the Changelog for a more complete list of changes.
.NET Core Support
We now support .NET Core in addition to .NET 4.5 target frameworks. This brings us up to date with the latest improvements in the .NET ecosystem and allow for exciting new features like .NET Core Runtime and much easier distribution of your games for Windows, macOS and Linux.
With this release MonoGame has moved away from traditional installers and has opted for using NuGet for all distribution of assemblies and tools. This also includes the new Visual Studio templates which are a VS extension.
Visual Studio 2019 and .NET Core CLI templates
We now have templates for both Windows and macOS versions of Visual Studio 2019 as well as templates for the .NET Core CLI tools.
SDK-Style Projects in the repository
Protobuild served us well in helping avoid manual synchronization of all our different platform projects. With the new SDK-style projects supported in .NET Core, VS2017, and VS2019 we can now easily maintain the projects and solutions in the repo.
Removed Portable Assemblies
The MonoGame.Framework.Portable and MonoGame.Framework.Content.Pipeline.Portable are no longer supported. This is mainly because Microsoft changed the assembly replacement rules needed to make them work in the new project system. We now recommend using MonoGame.Framework.DesktopGL and MonoGame.Framework.Content.Pipeline and disable the PrivateAssets to avoid copying any dependent assemblies.
An example on how to set it up can be found in the templates with "MonoGame NetStandard Library" and "MonoGame Pipeline Extension" templates respectively.