Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure reference isolation #4132

Merged
merged 1 commit into from
Jun 29, 2023
Merged

Ensure reference isolation #4132

merged 1 commit into from
Jun 29, 2023

Conversation

RussKie
Copy link
Member

@RussKie RussKie commented Jun 28, 2023

  • Use TestOnly.props only for test projects
  • Move analyzer references from BuildOnly.props to General.props
  • Remove BuildOnly.props as it contains unused references
Microsoft Reviewers: Open in CodeFlow

* Use TestOnly.props only for test projects
* Move analyzer references from BuildOnly.props to General.props
* Remove BuildOnly.props as it contains unused references
@RussKie RussKie marked this pull request as ready for review June 29, 2023 02:57
@RussKie RussKie enabled auto-merge (squash) June 29, 2023 02:58
@RussKie RussKie merged commit f415a2a into dotnet:main Jun 29, 2023
@ghost ghost added this to the 8.0 Preview7 milestone Jun 29, 2023
@@ -1,4 +1,6 @@
<Project>
<Import Project="$(MSBuildThisFileDirectory)\..\eng\packages\TestOnly.props" />
Copy link
Contributor

Choose a reason for hiding this comment

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

Why do we need test-related props in benchmarks?

Copy link
Member Author

Choose a reason for hiding this comment

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

The benchmarks (at least some of those) are, essentially, test projects, so they too have test-only dependencies. We can iterate on this in the future, but the main goal here is to ensure the shippable artifacts don't accidentally pull in test-only dependencies.

@RussKie RussKie deleted the ref_isolation branch June 29, 2023 23:52
@ghost ghost locked as resolved and limited conversation to collaborators Jul 30, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants