(adsbygoogle = window.adsbygoogle || []).push({});

NuGet Packages

Introduction to the UnityNuGet Project

NuGet is the package manager for .NET, designed to enable developers to share fundamental reusable code. As you may know, Unity uses its own package manager format (UPM). Traditionally, to use a NuGet package in Unity, UPM packages include the NuGet package as embedded DLLs. This approach can become problematic when two packages include the same DLL or different versions of a NuGet package. A robust solution is to create a shared NuGet package in UPM format that other packages can depend on.

Alexandre Mutel (xoofx) originally created the UnityNuGet project, which is now maintained by Borja Domínguez (bdovaz). This service converts NuGet packages to UPM format. The UnityNuGet registry server handles the packaging of these NuGet packages in a consistent and automated way, using proper naming under the org.nuget scope.

OpenUPM hosts a UnityNuGet server at https://unitynuget-registry.openupm.com. The service tracks the latest Docker release version and automatically deploys updates when a new version is released.

If you wish to update the tracked NuGet packages, please follow the instructions in the UnityNuGet documentation.

Using Uplinked UnityNuGet

Experiments

The UnityNuGet uplink is an experimental feature.

To improve convenience, the OpenUPM registry uplinks to the UnityNuGet registry, making it transparent for Unity users to consume UnityNuGet packages.

• The OpenUPM registry synchronizes with the UnityNuGet registry on an hourly basis.
• Package tarballs are hosted on our CDN server, ensuring fast access.
• You can view package details via https://package.openupm.com/org.nuget.some-package or by using the openupm-cli command openupm view org.nuget.some-package.

The integration comes with a few limitations:

• NuGet packages are neither searchable nor browsable on the OpenUPM website.
• Searching for NuGet packages via the OpenUPM registry's search endpoint will return "404 packages not found." This affects both the openupm-cli's search command and the Unity Package Manager's search interface. As a side effect:
  • NuGet packages will be invisible in the Unity Package Manager's "My Registries" section, although they remain visible in the "In Project" section.
  • The Unity console will display a warning "Error searching for packages" the first time you open the Package Manager.

To demonstrate the uplinks feature, we have created a staging package at https://github.com/openupm/com.example.nuget-consumer which includes:

• Installation of an OpenUPM package that depends on UnityNuGet.
• Resolution of potential assembly conflicts by disabling "Assembly Version Validation."

If you install a package via openupm-cli, the uplink is used by default— all packages under the org.nuget scope are resolved directly from the OpenUPM registry.

Using UnityNuGet Directly

In general, we recommend using the uplink feature to take advantage of the CDN and openupm-cli. However, if you wish to bypass the limitations mentioned above, you can use the UnityNuGet registry directly by adding it as a scoped registry in your manifest.json:

{
  "scopedRegistries": [
    {
      "name": "Unity NuGet",
      "url": "https://unitynuget-registry.openupm.com",
      "scopes": [
        "org.nuget"
      ]
    },
    // ... (other scoped registries, for example the OpenUPM registry)
  ]
}

List All UnityNuGet Packages

You can browse the curated list of UnityNuGet packages on the UnityNuGet GitHub repository.