Skip to content
This repository has been archived by the owner on Feb 23, 2024. It is now read-only.

Updating the SDK

kircher1 edited this page Jun 1, 2022 · 1 revision

When new versions of the SDK are published, they will be shown in Package Manager.

To be notified when new versions are available, watch for updates to the Changelog.

Migrating to 0.9.0+

Versions before the release of 0.9.0 were provided as a NuGet package and used a NuGet plugin for Unity to manage installation and updates of the SDK.

As of version 0.9.0, the SDK is available as a Unity package which can be installed and updated from within the editor using the Package Manager window.

To migrate from an older version of the SDK to 0.9.0 or newer, follow the steps below.

1. NuGet -> UPM

To migrate from the NuGet package to the NPM package:

  1. Remove the Microsoft.Maps.Unity NuGet package.
    • Nuget -> Manage Nuget Packages
    • Go to Installed tab
    • Uninstall Microsoft.Maps.Unity
  2. If no other NuGet packages are being used in the project, the NuGet plugin can be removed by deleting the following:
    • Assets\Nuget directory
    • Assets\Nuget.config
    • Assets\Packages directory
    • Assets\Packages.config
  3. Next, follow the steps here to install the latest version of the SDK via the Package Manager.

2. Fixing script errors due to GUID changes

Version 0.9.0 introduced various breaking changes due to moving components from the DLL to scripts.

An editor extension has been provided to automate the process of upgrading the GUIDs.

In the editor, go to Assets -> Maps SDK for Unity -> Upgrade Component GUIDs

Other breaking changes to APIs are not automated. If more information is required to resolve other errors in the scripts, refer to the Changelog for description of APIs that were modified.


Clone this wiki locally