Andrei Borodin

TFMs in the generated projects is currently commented because it needs to be present in the proj file. We can't even conditionally define it, because we need to import it...

Yeah, you should be able to move the project in that example to anywhere under "UnityProject"

Ok, so this corner case is the reason I previously added "Clean", take a look here: https://github.com/microsoft/MSBuildForUnity/blob/master/Source/MSBuildTools.Unity/Packages/com.microsoft.msbuildforunity/Editor/ProjectGenerator/MSBuildTemplates/MSBuildForUnity.Common.props.template There is a comment on line 33, uncomment that block and you should...

Also, we should update NuGet versions to also be incremented. This doesn't only mean for packaging, but also for consumption.

The change above didn't cover: - Mechanism for updating the templates used in generation that are part of MSBuildForUnity NPM package - Mechanism for keeping the NPM package.json version in...

We could possibly provide a field(s) on ProjectBuilder asset to specify directories to watch for changes.

Hi Bian, the project generator is a step towards unification of Unity and non-Unity development environment that will enable us to leverage projects shared between Unity and non-Unity projects, rely...

This is similar to the #67 issues, however, in that case the source lives outside of the Unity project but the C# project file has direct references to the current...

This is also similar to having one Unity project references projects generated in another Unity project but using the former's data.

Moving forward, everything will be updated to use the UnityPlatform/UnityConfiguration changes. Any reconciliation will happen for V1.