So MBINCompiler has been supporting .net 4 and .net 5 for quite a while now.
Unfortunately these have been out of support for quite a few years now (see https://endoflife.date/dotnet)
As part of keeping up with modern .Net versions, as of Monday, July 17th 2023 we will be removing builds of both .net 4 AND .net 5 (the current default build version), and replacing it with .net 6 and .net 7.
The primary un-version-named files (ie. MBINCompiler.exe and libMBIN.dll) will both be built for .Net 6 since it is the LTS version, and the .Net 7 supporting binary will be named as such.
Near the end of the year (no firm date as of yet), we will also roll out .Net 8 support as it's the next LTS version.
Please let me know if you have any concerns around this change, however most tool developers are aware of this and already support .Net 6, so there should be no issue with tool compatibility.
So MBINCompiler has been supporting .net 4 and .net 5 for quite a while now. Unfortunately these have been out of support for quite a few years now (see https://endoflife.date/dotnet) As part of keeping up with modern .Net versions, as of Monday, July 17th 2023 we will be removing builds of both .net 4 AND .net 5 (the current default build version), and replacing it with .net 6 and .net 7. The primary un-version-named files (ie.
MBINCompiler.exeandlibMBIN.dll) will both be built for .Net 6 since it is the LTS version, and the .Net 7 supporting binary will be named as such.Near the end of the year (no firm date as of yet), we will also roll out .Net 8 support as it's the next LTS version. Please let me know if you have any concerns around this change, however most tool developers are aware of this and already support .Net 6, so there should be no issue with tool compatibility.