Skip to content

Conversation

@CyrusNajmabadi
Copy link
Member

Followup to #79808.

Doing this allows them to be remotable to our OOP service.

editorConfigFileName: FileName);

UpdateOptions(options, solution, projects);
// TODO(cyrusn): Do we need to track this work in some way?
Copy link
Member

@jasonmalinowski jasonmalinowski Aug 9, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there also a risk of racing if multiple things are happening at once now too? Are we better off just making this a JTF.Run() and keeping it synchronous rather than introducing regressions here which we aren't going to want to investigate?

Copy link
Member

@jasonmalinowski jasonmalinowski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks fine other than that TODO about 'do we need to track this work'? Should we just keep that a synchronous JTF.Run() and come back to that later? Yes that might UI delay but we can invest in making that better later if needed, as opposed to introducing bugs now...

@CyrusNajmabadi CyrusNajmabadi merged commit eb3d589 into dotnet:main Aug 9, 2025
24 of 25 checks passed
@CyrusNajmabadi CyrusNajmabadi deleted the diagServiceAsync branch August 9, 2025 04:13
@dotnet-policy-service dotnet-policy-service bot added this to the Next milestone Aug 9, 2025
@RikkiGibson RikkiGibson removed this from the Next milestone Aug 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants