Jan Krivanek
C++ is a great point! - I haven't thought about that much. Lets return to it once we have some stronger opinion on the net.sdk What is your thoughts on...
Maybe first 1 important question I didn't put nowhere in this item or discussion: _Where can we afford to have the declaration of used analyzer?_ * Does it have to...
Related: #6944
Waiting for C# Dev Kit 1.3.x to age out (https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csdevkit), then we'll merge & ship `StableStringHash` overloads (including the one using FNV)
@MaceWindu this was side effect of previous changes. This currently doesn't meet bar for fixing - but we are leaving this open for upvotes.
In order to prevent breaking through the layering separation of SDK style projects you should be using `DisableTransitiveProjectReferences` (for ProjectReference) or `PrivateAssets` (for PackageReference). This will immediately uncover and prevent...
Based on current description - this is intended and desired behavior, so closing as 'not a bug'
@MIchaelRShea - do you have any quick idea on reason/remedy for this?
Some quick observations: Directory.Build.props: ```xml $(BaseOutputPath)$(Configuration)\ $(BaseOutputPath)$(Platform)\$(Configuration)\ ``` There are two possibilites how the artifacts/bin/shared/Release folder can be created: * $(Platform) == 'AnyCPU' * $(Platform) is empty And the second...
@AliveDevil You are relying on `Platform` property in Directory.Build.props, while it is set in the .csproj file. So unless this is passed as a global property by the platform negotiation...