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.
DDD can lead to dealing with non-generic references to generic instances of types. Generically mapping these instances or generically calling code with them is not straightforward. I present how it can nonetheless be unobtrusively achieved with a general visitor-like pattern.
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.
If 3rd party assemblies unnecessarily target an inconvenient bitness, either convince the 3rd party of AnyCpu or force AnyCpu on the assembly yourself (with permission from legal).
Speed up development of dependent nuget package chains by creating sibling projects that use ProjectReference instead of PackageReference for instantaneous feedback.
DDD can lead to generic types that are hard to import to. This technique can be used to make a generic call with multiple type arguments when each type argument is supplied individually, e. g. from an import into a domain model.