Upgrade to GeoBlazor Pro

If you have started an application with the free GeoBlazor Core library, and later want to take advantage of the expanded feature set and support of the GeoBlazor Pro library, here are the simple set of steps to upgrade your projects.

  1. Visit https://licensing.dymaptic.com, and generate a new GeoBlazor Pro license key.

  2. Replace the GeoBlazor Core key in your appsettings.json or secrets.json with the new Pro key.

    {
  "ArcGISApiKey": "THIS_DOES_NOT_CHANGE",
  "GeoBlazor": {
    "LicenseKey": "THIS_SHOULD_BE_YOUR_NEW_PRO_KEY"
  }
} 

    {
  "ArcGISApiKey": "THIS_DOES_NOT_CHANGE",
  "GeoBlazor": {
    "LicenseKey": "THIS_SHOULD_BE_YOUR_NEW_PRO_KEY"
  }
}

  3. Remove the NuGet package reference for GeoBlazor Core.

    From command line:

    dotnet package remove dymaptic.GeoBlazor.Core

    dotnet package remove dymaptic.GeoBlazor.Core

    Or directly in the .csproj file:

    <ItemGroup>
  <!-- DELETE THIS NEXT LINE --->
  <PackageReference Include="dymaptic.GeoBlazor.Core" Version="4.1.0" />
</ItemGroup>

    <ItemGroup>
  <!-- DELETE THIS NEXT LINE --->
  <PackageReference Include="dymaptic.GeoBlazor.Core" Version="4.1.0" />
</ItemGroup>

  4. Add the NuGet package reference for GeoBlazor Pro.

    From command line:

    dotnet package add dymaptic.GeoBlazor.Pro

    dotnet package add dymaptic.GeoBlazor.Pro

    Or directly in the .csproj file:

    <ItemGroup>
  <!-- ADD THIS NEXT LINE --->
  <PackageReference Include="dymaptic.GeoBlazor.Pro" Version="4.1.0" />
</ItemGroup>

    <ItemGroup>
  <!-- ADD THIS NEXT LINE --->
  <PackageReference Include="dymaptic.GeoBlazor.Pro" Version="4.1.0" />
</ItemGroup>

  5. Replace the AddGeoBlazor line in Program.cs with AddGeoBlazorPro.

    builder.Services.AddGeoBlazorPro(builder.Configuration);

    builder.Services.AddGeoBlazorPro(builder.Configuration);

  6. Namespace imports are handled automatically — the GeoBlazor Pro NuGet package provides implicit global using directives for all Pro namespaces. You can remove any existing @using dymaptic.GeoBlazor.Pro.* lines from _Imports.razor, as they are no longer needed.

  7. CSS stylesheets are also handled automatically — GeoBlazor injects both Core and Pro CSS via Blazor's <HeadContent> component when a MapView or SceneView renders. You can remove any existing <link href="_content/dymaptic.GeoBlazor.Pro" /> lines from your App.razor or index.html.

    Blazor Hybrid (MAUI) exception: <HeadContent> is not supported in hybrid apps. You must keep the manual CSS link in wwwroot/index.html:

    <link href="_content/dymaptic.GeoBlazor.Pro"/>

    <link href="_content/dymaptic.GeoBlazor.Pro"/>

  8. Finally, we always suggest to clear out bin and obj folders, as well as open the browser developer tools and choose disable cache once after an upgrade, to ensure that all the new assets are being loaded correctly. If you encounter any issues, join our Discord server or contact us for support.