timsparkles

I'd love to see some figures on how much time is likely to be saved by reusing nodes. I suspect it's in the sub-second range and thus only has an...

We are switching to solution generation, and none of the solution generators we have found have support for sln-level ProjectDependencies. We tried creating a shortcut OrderingOnly="true" attribute and a custom...

@jhudsoncedaron I find that SelfContained and SkipGetTargetFrameworkProperties cause problems . Either of them will push the referenced project into a separate batch and a separate node in the dependency graph,...

@jhudsoncedaron for us, it's simpler to just omit those problematic properties. They don't seem to have any impact on the build when omitted. That may be only because we're still...

@jhudsoncedaron I just hope this discussion demonstrates to the msbuild team that there exists an urgent need for a project-level ordering-only dependency declaration feature.

I'm still not seeing anything related to inheritance or base class on the SetUpFixture documentation page FWIW

My preference here is that the container would immediately expand to fit the content when it is sized too small, similarly to how it immediately shrinks to fit the content...

https://github.com/MicrosoftDocs/feedback/issues/3785 is a specific instance of this issue. https://github.com/MicrosoftDocs/feedback/issues/3741 describes a potential fix.

I confirm that this bug also affects non-SDK .NET Framework projects, as suggested by the last paragraph of vatsan-madhavan's comment from Jul 3, 2020. I disagree with the assessment that...

I successfully worked around this issue by replacing: `some\path\including\$(MSBuildProjectName)\` with `$(MSBuildProjectName)` `$(AssemblyName)` `some\path\including\$(OutputDirectory)\` Obviously this will not work for you if you need `$(AssemblyName)` to differ from `$(MSBuildProjectName)`.