nuget.org support finally provided a resolution on my account issue and I was able to regenerate my publishing keys.
As a result, the 6.0m12 release (6.0.0-pre500) nuget packages are now finally available on nuget.org
Need directions?
nuget.org support finally provided a resolution on my account issue and I was able to regenerate my publishing keys.
As a result, the 6.0m12 release (6.0.0-pre500) nuget packages are now finally available on nuget.org
There were a few things I left out of the previous announcement that I'll use this post to address.
Firstly, the 6.0m12 release of MapGuide Maestro formally drops all Fusion editor support for integration with Google Maps tiles and services. We no longer support Google Maps integration in Fusion and the editor in previous releases gave the false impression that this is still possible. That is no longer the case with this release.
Secondly, the more important thing (and the subject of this post) is that if you are using the Maestro API and consume this through nuget packages from nuget.org you may be wondering why there are no new versions?
The answer to that one is simply: My nuget package publishing keys have expired and something in the nuget.org website or something with my nuget.org account is preventing me from regenerating these keys or to generate a fresh set. As a result, I currently cannot upload any new nuget packages to nuget.org
But do not fret, because there is an alternative solution.
As part of the MapGuide Maestro release on GitHub, the nuget .nupkg files are also included
From here, you can set up a local directory-based nuget package source, drop the .nupkg files into it and the this version of the package is available to install in your Visual Studio solution.
If/when I get a resolution on this publishing key matter, I will upload the .nupkg files for this release and make another announcement. Until then, this local package source is a suitable workaround.
Next stop on the tour: A new release of MapGuide Maestro
This release includes the following notable changes.
This release improves the MapGuide Open Source 4.0 authoring experience with support for the new label justification setting for basic stylization labels.
This setting is part of the new v4.0.0 Layer Definition XML schema, whose .xsd file is now also included with this release (so XML validation against this schema will work)
This release includes several enhancements to the Fusion Flexible Layout editor to support various features that can be taken advantage of when loaded into a mapguide-react-layout viewer. These new enhancements are accessible from the layout settings panel and require the latest release of mapguide-react-layout to leverage these new features.
The Manage Custom Projections button opens up a new dialog that lets you manage and pre-register custom proj4 definitions for your application. By pre-registering these definitions in the Flexible Layout document itself, you can avoid needing to perform a epsg.io lookup for any projections found in the viewer init process that is not EPSG:4326 or EPSG:3857
The Manage Settings button opens up a different dialog that lets you managed the app settings in the Flexible Layout document. These are arbitrary key/value pairs that your mapguide-react-layout viewer will be initialized with and your viewer code can read such settings at runtime to control and drive whatever custom functionality you may have.