v0.8.3 HotFix Release

This release fixes issues in v0.8.2 release:

• Remove noisy Debug.Log for native binaries not being yet compatible with MSBuildForUnity (Logging will be re-enabled as part of #75)
• Fix errors when project path contains spaces.

v0.8.2 HotFix Release:

This release fixes a few issues in v0.8.1 release:

• It corrects the times that build/clean is done to ensure the appropriate dependencies are pulled in
• It fixes the issue of pulling in NuGet packages in IntegratedDependencies under .NET Standard 2.0

v0.8.1 Release:

This first release comes with very core functionality of MSBuildForUnity. You can express your Unity project's dependencies in the form of MSBuild PackageReferences and ProjectReferences, and then have them be built and resolved into your Unity project. Take a look at one of the samples to better understand how this works.

Features:

• Build MSBuild projects insides Unity
• Add ProjectReferences and PackageReferences to MSBuild project files and pull them in as dependencies into the Unity project
• Support per-Unity player dependencies
• Generate MSBuild project structure based on the current Unity project
• Compile Unity components into DLLs using the generated MSBuild project structure
• Debug compiled DLLs with PDBs and source inside Unity Editor

To get started, modify your Unity's Packages/manifest.json file as so:

• Add the following near the top of the file:

  "scopedRegistries": [
      {
          "name": "Microsoft",
          "url": "https://pkgs.dev.azure.com/UnityDeveloperTools/MSBuildForUnity/_packaging/UnityDeveloperTools/npm/registry/",
          "scopes": [
              "com.microsoft"
          ]
      }
  ],

• Add the following to the dependencies section of the file:

    "com.microsoft.msbuildforunity": "0.8.3"