Gotcha with .globalconfig and Visual Studio
VS will always apply a `.globalconfig`, not just when analyzers are activated like the CLI build does. Use a different name and explicit inclusion to get consistent behavior.
Advanced MSBuild: Auto-setup test projects
You can minimize the effort of creating new test projects according to your project's conventions by defining some global default MSBuild properties. A new test project csproj will then be a five-liner consisting only of the SDK and TFM.
Advanced MSBuild: The Right Way™ of writing .props files
Following a couple of simple rules will give you robust project/props/targets files that will just work.
Advanced MSBuild: Adding a ProjectReference sibling project to a PackageReference project
Speed up development of dependent nuget package chains by creating sibling projects that use ProjectReference instead of PackageReference for instantaneous feedback.
Advanced MSBuild: project file as single source of truth for build and runtime
It is possible to define build parameters in a way that is accessible at runtime by declaring custom AssemblyAttribute entries in your csproj file.
Advanced MSBuild: multi-API-version compatibility without code duplication
Maintain functionality against different versions of an external library without code duplication by using preprocessor directives.
Advanced MSBuild: changing the build output directory, completely
To fully change the build output folder of a project, you need to redefine three project properties.
Advanced MSBuild: Ignoring Bitness when building Plugins
When developing plugins for an application that is shipped as both 32 and 64 bit, it may be possible to publish a single artifact working with both by building as AnyCpu, ignoring the MSB3270 warning.
Advanced MSBuild: Introduction
Knowing MSBuild can help you remove code duplication, enforce consistency in a large repo and improve developer experience.
Nuget Packaging Series 2: Beware of DLL version conflicts
Putting assemblies with different TFMs in the same nuget package can lead to runtime assembly loading errors because of transitive assembly reference version conflicts.