FileShare.Noneproperty. The question is - can we create a bug for this and change to
FileShare.Read? As we have a large amount of builds per day these intersections became very common for us, so it will be great to be fixed inside the root tool instead of doing workarounds and I believe will help others who face such issue.
FileShare.Nonecould be a feature rather than bug.
DotNetCoreBuildSettingsare we allowed to use
any? According to this
anyis a valid value, isn't it? https://github.com/dotnet/runtime/blob/master/src/libraries/pkg/Microsoft.NETCore.Platforms/runtime.json
win-x64, but I would like this assembly to be available for .netcore3.1 projects running on Linux as well. Do I have to produce two separate nuget packages?
PublishArtifactsshould be done in background, TeamCity docs at https://www.jetbrains.com/help/teamcity/build-script-interaction-with-teamcity.html#BuildScriptInteractionwithTeamCity-PublishingArtifactswhiletheBuildisStillinProgress
FileShare.Readissue\feature - cake-build/cake#2745