Any assembly that contains types (such as classes or structs) that depend on types in another assembly must have a reference to the other assembly. You can control the references between assemblies by configuring Assembly Definition properties in the Inspector window. For more information, refer to Assembly definition properties reference.
By default, the predefined assemblies reference all other assemblies, including those created with Assembly Definitions (1) and precompiled assemblies added to the project as plugins (2). Custom assemblies you create with an Assembly Definition asset automatically reference all precompiled assemblies (3):
In the default setup, classes in the predefined assemblies can use all types defined by any other assemblies in the project. Likewise, assemblies you create with an Assembly Definition asset can use all types defined in any precompiled (plug-in) assemblies.
To prevent a custom assembly being automatically referenced by the predefined assemblies, deselect the Assembly Definition’s Auto Referenced property in the Inspector. This means the predefined assemblies don’t recompile when you change code in the assembly but also means the predefined assemblies can’t use code in this assembly directly.
To prevent a plugin assembly from being automatically referenced by either predefined or custom assemblies, deselect the Auto Referenced property in the Plugin Inspector for a plugin asset. You can still add an explicit reference to the plug-inA set of code created outside of Unity that creates functionality in Unity. There are two kinds of plug-ins you can use in Unity: Managed plug-ins (managed .NET assemblies created with tools like Visual Studio) and Native plug-ins (platform-specific native code libraries). More info
See in Glossary from a custom assembly, refer to Referencing a precompiled plug-in assembly.
Unity doesn’t allow the following types of references:
To use code from another assembly, you must add a reference to the other assembly in the Assembly Definition asset.
To add a reference to another assembly:
Select the Assembly Definition for the assembly that requires the reference to view its properties in the InspectorA Unity window that displays information about the currently selected GameObject, asset or project settings, allowing you to inspect and edit the values. More info
See in Glossary.
In the Assembly Definition References section, click the + button to add a new reference.
Assign the Assembly Definition asset to the newly created slot in the list of references.
Enabling the Use GUIDs option allows you to change the filename of the referenced Assembly Definition asset without updating references in other Assembly Definitions to reflect the new name.
Note: GUIDs must be reset if the metadata files for the asset files are deleted or you move the files outside the Unity Editor without also moving the metadata files along with them.
By default, all custom assemblies you create with Assembly Definitions automatically reference all precompiled assemblies. This means Unity recompiles all your assemblies when you update any one of the precompiled assemblies, even if the code in the assembly is not used.
To avoid this extra overhead, you can override the automatic references and specify references to only those precompiled libraries the assembly actually uses:
Select the Assembly Definition for the assembly that requires the reference to view its properties in the Inspector.
In the General section, enable the Override References option.
The Assembly References section of the Inspector becomes available when Override References is checked.
In the Assembly References section, click the + button to add a new reference.
Use the drop-down list in the empty slot to assign a reference to a precompiled assembly. The list shows all the precompiled assemblies in the project for the currently active platform in Build ProfilesA set of customizable configuration settings to use when creating a build for your target platform. More info
See in Glossary. (Set the platform compatibility for a precompiled assembly in the [Plugin Inspector].)
Click Apply.
Repeat for each platform for which you build your project.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.