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

Switch to Microsoft.DotNet.XUnitExtensions #6638

Merged
merged 1 commit into from
Jul 15, 2021

Conversation

rainersigwald
Copy link
Member

Let's delete a bunch of code from our repo and replace it with the modern version from Arcade.

We can't delete our assembly entirely because Arcade doesn't have the Fixture stuff that we depend on fairly heavily.

Let's delete a bunch of code from our repo and replace it with the
modern version from Arcade.

We can't delete our assembly entirely because Arcade doesn't have
the Fixture stuff that we depend on fairly heavily.
Copy link
Member

@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.

Understanding check:
We'd previously copied a lot of code from Arcade. Here, you're deleting that code and adding a reference to Arcade so don't have to carry it around and get updates for (almost) free.

If someone had built our repo just before this, then pulled in this change, did not build, went offline, and tried to build again, that would fail, correct? I don't think we should care—just trying to think of edge cases.

@@ -32,6 +32,7 @@
<!-- DotNetCliVersion MUST match the dotnet version in global.json.
Otherwise, this version of dotnet will not be installed and the build will error out. -->
<DotNetCliVersion>$([System.Text.RegularExpressions.Regex]::Match($([System.IO.File]::ReadAllText('$(MSBuildThisFileDirectory)..\global.json')), '"dotnet": "([^"]*)"').Groups.get_Item(1))</DotNetCliVersion>
<MicrosoftDotNetXUnitExtensionsVersion>6.0.0-beta.21329.2</MicrosoftDotNetXUnitExtensionsVersion>
Copy link
Member

Choose a reason for hiding this comment

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

Will this be auto-updated by darc?

Also, is there some way we can specify the version once and have it appear both here and in Version.Details.xml?

Copy link
Member Author

Choose a reason for hiding this comment

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

Will this be auto-updated by darc?

Yes, I expect this to be updated by our existing arcade->msbuild darc subscription.

Also, is there some way we can specify the version once and have it appear both here and in Version.Details.xml?

I am not aware of one. Darc's design requires having it in two places updated by tooling.

@rainersigwald
Copy link
Member Author

We'd previously copied a lot of code from Arcade. Here, you're deleting that code and adding a reference to Arcade so don't have to carry it around and get updates for (almost) free.

Correct.

If someone had built our repo just before this, then pulled in this change, did not build, went offline, and tried to build again, that would fail, correct? I don't think we should care—just trying to think of edge cases.

Correct (as with any package addition or version change).

@rainersigwald rainersigwald added the merge-when-branch-open PRs that are approved, except that there is a problem that means we are not merging stuff right now. label Jul 14, 2021
@benvillalobos benvillalobos merged commit dfd2be7 into dotnet:main Jul 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merge-when-branch-open PRs that are approved, except that there is a problem that means we are not merging stuff right now.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants