Thank you for helping us improve the quality of Unity Documentation. Although we cannot accept all submissions, we do read each suggested change from our users and will make updates where applicable.
CloseFor some reason your suggested change could not be submitted. Please <a>try again</a> in a few minutes. And thank you for taking the time to help us improve the quality of Unity Documentation.
CloseStores the path to the Roslyn global config file.
You can define a project-wide analyzer configuration in a file with the .globalconfig file extension. Use key-value pairs to configure the default behavior of all files in your project. If a file with this extension is present, Unity automatically detects it and stores the path in this property.
Use this global config file in the same way as a ruleset file. Create a file named "Default.globalconfig" in your root asset folder to apply the configuration to all predefined assemblies and any assemblies that Unity builds with .asmdef files.
You can override the options for some predefined Unity assemblies by creating a .globalconfig file in the root asset folder with the name [PredefinedAssemblyName].globalconfig.
If a [PredefinedAssemblyName].globalconfig is present, the options specified in that file are used instead of the ones in the Default.globalconfig (if present).
Only these .globalconfig files are permitted inside the root asset folder:
- Default.globalconfig
- Assembly-CSharp.globalconfig
- Assembly-CSharp-firstpass.globalconfig
- Assembly-CSharp-Editor.globalconfig
- Assembly-CSharp-Editor-firstpass.globalconfig
It is also possible to override the options for each assembly definition, by creating a .globalconfig file in the same folder as its .asmdef file.
There are no name restrictions in this case, but it is a good practice to follow the rule [AssemblyDefinitionName].globalconfig.
If a globalconfig file is present for assembly definition, the options specified in that file are used instead the ones in the Default.globalconfig (if present).
If multiple keys with the same name are present in the same config file, Unity uses the last entry in the file for that key.
Config files are not additive: you can't have a Default.globalconfig that sets some common value and has a subset for a specific assembly.
If you add a global config override for PredefinedAssemblyName or an assembly definition, that file should contain all the keys-value pairs.
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.