BrianPeek/NuGet2Unity
Repackage NuGet package as a .UnityPackage for import into a Unity project
- Users starred: 21
- Users forked: 5
- Users watching: 21
- Updated at: 2020-05-15 23:37:59
NuGet2Unity
This project is no longer under active development.
A .NET Core app to package a NuGet package (and dependencies) as a .UnityPackage for import into a Unity 2018 (or higher) project. This will build a package that should be compatible with the following Unity player settings (Player Settings -> Other Settings -> Configuration):
| Setting | Value |
|---|---|
| Scripting Runtime Version | .NET 4.x Equivalent |
| Scripting Backend | Mono or IL2CPP |
| Api Compatibility Level | .NET Standard 2.0 |
Build
It is assumed you have .NET Core 2.1 installed. If not, you can download from here. Once installed, from the src directory, run the standard dotnet build command.
Usage
Assuming you are in the src directory, simply run the standard dotnet run command with the following options:
| Switch | Description |
|---|---|
| -n, --nugetpackage | Required. NuGet package to repackage |
| -v, --version | Version of NuGet package to use |
| -p, --unityproject | Path to the Unity project to include with this package |
| -m, --includemeta | Include .meta files from the Unity project |
| -o, --outputpath | Path to save the .unitypackage |
| --verbose | Maximum verbosity |
| --skiplinkxml | Do not add a link.xml to package |
| --help | Display this help screen. |
| --version | Display version information. |
Example
Let's say you wanted to download and package the latest version of the WindowsAzure.Storage NuGet package to a Unity package in the current directory. Here's what that would look like (note the -- argument which ensures the switches get passed to the app itself, not the dotnet command:
link.xml
Please note that, by default, a link.xml file will be generated which preserves all namespaces from all assemblies in the NuGet package and its dependencies. This may lead to large projects and longer build times. If this is a problem, please use the --skiplinkxml switch and determine which assemblies and namespaces (if any) should be included and manually add them to your link.xml file.
dotnet run -- -n WindowsAzure.Storage
Packages
Check out our Sandbox site for some repackaged Azure SDKs that were built using this tool.
