Good news for you! As part of the overhaul to use vanilla SWIG to generate all of our managed bindings, the .net binding is now built as a set of netstandard2.0 assemblies, so it will work on:
- "legacy" .net Framework 4.x - .net core (all versions that support netstandard2.0) - .net 5 and every version going forward The .nuget packages are now also built the "proper way" so unmanaged native dlls are automatically handled and copied by MSBuild. No more hacky post-build "copy unmanaged dlls" commands required. The current 4.0 beta 2 ships the .nuget package files inside the $INSTALL/Web/nuget folder. Once we reach 4.0 final, these nuget packages will also be published to nuget.org, so no matter how you slice it, the developer story for building MapGuide .net applications in 4.0 will always be: Install the relevant nuget packages, whether that be local .nuget package files that are shipped with the release or through nuget.org However, I must stress this very important point: Do not take netstandard2.0 support to imply that this will also work for .net on non-Windows platforms. Linux .net support may or may not be the case come 4.0 final release, but OSX and any other non-Windows platforms are a hard and definite no. - Jackie You wrote: Hi Jackie, Is there some plan to migrate Mapguide on .net8 (or higher) ? Cheers, Bruno Scott
_______________________________________________ mapguide-users mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/mapguide-users
