I did some digging, after updating to Content Pipeline v3.7.0 from v1.1.0 with NuGet, this is what I get when executing build command manually:
H:\Visual Studio\Projects\Test\Test\Content>"C:\Program Files (x86)\MSBuild\MonoGame\v3.0\Tools\MGCB.exe" /@:"H:\Visual Studio\Projects\Test\Test\Content\Content.mgcb" /platform:Windows /outputDir:"H:\Visual Studio\Projects\Test\Test\Content\bin\Windows" /intermediateDir:"H:\Visual Studio\Projects\Test\Test\Content\obj\Windows"
Build started 09-Sep-19 05:06:08 PM
Failed to load assembly 'H:/Visual Studio/Projects/Test/packages/MonoGame.Extended.Content.Pipeline.3.7.0/lib/netstandard2.0/MonoGame.Extended.Content.Pipeline.dll': Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
H:/Visual Studio/Projects/Test/Test/Content/fonts/gui.fnt: error: Failed to create importer 'BitmapFontImporter'
Skipping H:/Visual Studio/Projects/Test/Test/Content/fonts/gui_0.png
Build 2 succeeded, 1 failed.
Time elapsed 00:00:00.14.
After plumbing around with a debugger I've managed to print out what's going on internally:
Unhandled Exception: System.MissingMethodException: Method not found: 'Microsoft.Xna.Framework.Content.Pipeline.ContentStatsCollection MonoGame.Framework.Content.Pipeline.Builder.PipelineManager.get_ContentStats()'.
at MGCB.BuildContent.Build(Int32& successCount, Int32& errorCount)
at MGCB.Program.Main(String args)
The exception is thrown by
My project targets .NET 4.7.2, my MonoGame version is 3.7.1 (was tested on 3.7.0 as well), my MonoGame.Extended version is 3.7.0 - NuGet latest at the time of writing.
What's baffling is that this property exists in the decompiler view
Here's some more info on the subject, as it seems assemblies are being loaded from a directory where lib from NuGet is located. I'm even more confused as I keep getting the feeling that it's a user fault?
Call stack: https://pastebin.com/xd0rWHBN
Contents of LoaderExceptions at the top of the call stack: https://pastebin.com/vWiCftSk
Looks like I've solved the problem for myself. I had to manually add the following to the mgcb file.
That got it building again.
However, after doing that, I was experiencing the issue that got solved in here: