Skip to content

Conversation

@MichalPavlik
Copy link
Member

Fixes #7684

@MichalPavlik MichalPavlik requested a review from AR-May June 8, 2022 13:37
Copy link
Contributor

@Forgind Forgind left a comment

Choose a reason for hiding this comment

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

I'm curious if it'd be better to move some of these APIs to internal rather than experimental, but I think this is fine.

On the other hand, first flaky failure of MSBuildServerTest? I'm not feeling great about that...

Copy link
Member

@AR-May AR-May left a comment

Choose a reason for hiding this comment

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

This change looks good.
I wonder, why don't we use the new attribute for the experimental in parallel with the namespace change. We would need ifdefs to turn it on only for .net core msbuild. It could be in this PR, or we might create one more for this change.

@AR-May
Copy link
Member

AR-May commented Jun 16, 2022

Decided not to use the new attribute to make testing of MSBuild server feature easier and separate two different stories: MSBuild server and experimental attribute.

@AR-May AR-May merged commit 39a56d0 into feature/msbuild-server Jun 16, 2022
@baronfel baronfel deleted the dev/mipavlik/msbuild-server-experimental-api branch March 20, 2025 15:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants