Development

To run most CLI tools, you need a couple of environment variables to be set. These can be found in .env.dist. Ensure these are loaded in your environment. There are a couple of ways to do that:

1. Export the variables in .env.dist manually:
   1. Using $env:FOO = 'Bar' (PowerShell only)
   2. Using SET FOO=Bar (Windows Command Prompt only)
   3. Using export FOO=BAR (Bash and compatible shells only).
      • With Bash, you can also put these in your .bashrc to not have to do this every time, if desired.
   4. Prepend the variables in .env.dist to the command using FOO=BAR BAZ=CUX dotnet ... (Bash and compatible shells only).
2. Copy .env.dist to .env, fill in the variables to your liking, and use something like direnv to automatically load them into your environment. (That way you can use the same configuration for native and container builds.)

Installing Unity NuGet Packages

After all necessary variables are in your environment, in the project root folder:

dotnet msbuild -target:PostProcessDotNetPackagesForUnity -restore NuGetDependencies/Unity/

After post-processing finishes, you can start or focus the Unity window of your project and let Unity import the dependencies.

Run Globally

If you want to check for analyzer errors across the codebase in one go, run:

dotnet build