The solution has two projects the FreeImagePipline and a TestFreeImage.OpenGL.
Everything is standard(ish) from the templates except for Line 14 in the FreeImageEditImporter.cs that just allocates some mapdata using FreeImage.Standard.
So my observation is that i can’t do anything with freeimage in the pipeline extension 3.8 but it worked in 3.7.
I’m guessing it’s something easy like i have to tell the FreeImage.Standard dll to work with .Net Core 3.1 in some capacity but i have no idea how… or why
Interestingly enough it built when I used the mgcb editor, it did not build when I used the mgcb from the command line. The error message seems to indicate that it has difficulties loading a native .dll so maybe the editor is able to load it because it’s built with the .NET windows SDK? Hard to say, but my gut feeling says that it’s likely there’s some native dependency issue at play here.
I don’t know exactly what you intend to do with FreeImage, but maybe you could consider using ImageSharp instead? It’s built in pure .NET so dependency issues on native .dll’s are not something you have to struggle with. It’s fairly multifunctional. Maybe a tad slower than the native alternatives, but probably not by much. Just something to consider. https://github.com/SixLabors/ImageSharp
The issue was closed with with this explenation below. I dont know why it changed between 3.7 and 3.8 but i dont care any more as i rewrote my processing step with ImageSharp as surgested by @persn
"Since MGCB also uses freeimage, and you are referencing another freeimage version, you will cause a lot of conflict between those 2 native libs so its no wonder that stuff starts crashing right away.
If you really wanna use one of the same native libraries MonoGame.Content.Pipeline already uses, you are gonna have to either reference the native library already in the MG.C.P folder or make your pipeline extension create another process."
Can someone assist in solving this problem and explain what is going on? (so a newbie can understand).
MGCB tool used to work fine for me, but couple of days ago I started receiving this error as well.
I installed it using dotnet tool comand.