Daniel Plaisted
Daniel Plaisted
Thanks for the pointer to #61 @khellang. Based on reading the discussion there, I've fixed the rule for cases where there are comments or compiler directives at the end of...
It looks like this also prevents the workload fallback from working during an update.
I don't think I addressed the last bit: > Separately, we probably shouldn't print the message "Successfully updated workload(s):" when no workloads have been updated. We should probably instead print...
> All of the requested changes are in @dsplaisted though we want this to go into 7.0.100 as well, it seems this is going to pick up other depended upon...
Do you want us to go ahead and review this? It's marked as a draft PR.
Possible solution: If the `RuntimeIdentifier` is specified on the command line, allow the `TargetFramework` from the command line to flow to the restore operation, since the `RuntimeIdentifier` being passed to...
@nkolev @dotnet/nuget-team I'm not sure how to fix this, I think we need to have a discussion with the NuGet team. I thought that the issue had to do with...
I don't think we have any real plans to fix this. From the command line, the target would probably be called only once if you ran `dotnet publish`. If it's...
@damien78 Could you try setting the `RuntimeIdentifier` property instead of `RuntimeIdentifiers`? Just a guess, but that might fix the issue.
> From the logs, I can conclude that the failing tests run on `Windows.Amd64.VS2022.Pre.Open`. From https://helix.dot.net/#Test-Internal-Windows I can see that it contains VS 17.3.0-pre.2 (released June 14, 2022). I tried...