Add definition how to#
Add definition code#

For projects, these are considered direct dependencies for packages, these are indirect, or transitive, dependencies. Projects and packages use the dependencies attribute in their manifests to define the set of packages they require.

Unity compiles assemblies in an order determined by their dependencies In the context of the Package Manager, a dependency is a specific package version (expressed in the form that a project or another package requires in order to work. For example, you can combine the scripts from all the Editor folders in your project in their own assembly, no matter where those folders are located. To include scripts from a non-child folder in an existing assembly, create an Assembly Reference asset in the non-child folder and set it to reference the Assembly Definition asset that defines the target assembly. Unity also includes scripts in any child folders in the same assembly, unless the child folder has its own Assembly Definition or Assembly Reference asset. Unity takes all of the scripts in a folder that contains an Assembly Definition asset and compiles them into an assembly, using the name and other settings defined by the asset. Then create Assembly Definition assets to specify the assembly properties.

Add definition code#

To organize your project code into assemblies, create a folder for each desired assembly and move the scripts that should belong to each assembly into the relevant folder. Assembly Definition Reference properties.Getting assembly information in build scripts.Finding which assembly a script belongs to.Defining symbols based on project packages.Referencing a precompiled, plugin assembly.Creating an Assembly Definition Reference asset.

Add definition how to#

This section discusses how to create and set up Assembly Definition and Assembly Reference assets to define assemblies for your project: Similarly, because Library doesn’t depend on any other assemblies, you can more easily reuse the code in Library in another project. Because Main references Stuff and not the other way around, you know that any changes to the code in Main cannot affect the code in Stuff. The above diagram illustrates how you might split up the code in your project into multiple assemblies. Scripts in the assemblies you define for your project are no longer added to the default assemblies and can only access scripts in those other assemblies that you designate.

All scripts are compiled for all platforms.īy defining assemblies, you can organize your code to promote modularity and reusability.

Any script can directly access types defined in any other script, which can make it more difficult to refactor and improve your code.

Every time you change one script, Unity has to recompile all the other scripts, increasing overall compilation time for iterative code changes.

This arrangement works acceptably for small projects, but has some drawbacks as you add more code to your project: (Unity also creates a few smaller, specialized predefined assemblies.)

NET for general information about assemblies in C#.īy default, Unity compiles almost all of your game scripts into the predefined assembly, Assembly-CSharp.dll. More info See in Glossary into assemblies.Īn assembly is a C# code library that contains the compiled classes and structs that are defined by your scripts and which also define references to other assemblies. Assembly Definitions and Assembly References are assets that you can create to organize your scripts A piece of code that allows you to create your own Components, trigger game events, modify Component properties over time and respond to user input in any way you like.