Jan Krivanek
> Ok, should I file another issue in dotnet/msbuild then? Yes please - move or copy to dotnet/msbuild
[Internal communication related to this](https://teams.microsoft.com/l/message/19:[email protected]/1728680077070?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&groupId=4ba7372f-2799-4677-89f0-7a1aaea3706c&parentMessageId=1728680077070&teamName=.NET%20Developer%20Experience&channelName=MSBuild&createdTime=1728680077070)
We should check the appearance of the `suggestion` level as well, but otherwise this feels ready to go!
@ladipro this PR will need `RequiresSymbolicLinksTheory` - can you please add it (reusing the `RequiresSymbolicLinksFact`)
@Nirmal4G do you plan to continue work on this PR or should that be closed? (a new one can allways be open - which might as well be quickes solution...
``` Build started at 3:15 PM... 1>------ Build started: Project: Microsoft.CodeAnalysis.Workspaces.MSBuild.BuildHost, Configuration: Debug Any CPU ------ 2>------ Build started: Project: InteractiveHost64, Configuration: Debug Any CPU ------ 3>------ Build started: Project:...
https://github.com/dotnet/msbuild/pull/10172 was operating in that area. On the other hand `SubmitBuildRequest` (which got the exception) was untouched by the refactoring **Edit:** running through the `SubmitBuildRequest` and all the code populating...
FYI @marcpopMSFT
Another area: * [ ] Replay improvements. * ability to mount new custom checks to the replay * ability to specify custom editorconfig to tune the level of checking This...
@JaynieBai - do you mean that `dotnet workload restore` does not pass through the `/p` commandline argument to the msbuild execution? @joeloff - is the `workload` command expected to pass-through...