-
Notifications
You must be signed in to change notification settings - Fork 199
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
Update dependencies and workaround dotnet/sdk#2976 #238
Conversation
natemcmaster
commented
Feb 22, 2019
•
edited
Loading
edited
- Update to latest extensions, corefx, and core-setup build
- Workaround All packages targeting netcoreapp3.0 have a 'Microsoft.NETCore.Platforms' dependency in nuspec sdk#2976
- Update xunit to 2.4.1. (required to consume latest Microsoft.AspNetCore.Testing)
- Add workaround to resolve conflicts between SDK and dependency versions
- Remove NETStandard package version override
Ready to merge, just waiting for review approval. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we move aspnet/Extensions to Xunit 2.4.1
and (then) the other repos?
@@ -128,8 +128,7 @@ | |||
<VSIX_MicrosoftVisualStudioLanguageServicesPackageVersion>3.0.0-beta2-18612-05</VSIX_MicrosoftVisualStudioLanguageServicesPackageVersion> | |||
<VSIX_MicrosoftVisualStudioLanguageServicesRazorRemoteClientPackageVersion>3.0.0-beta2-18612-05</VSIX_MicrosoftVisualStudioLanguageServicesRazorRemoteClientPackageVersion> | |||
<XunitAnalyzersPackageVersion>0.10.0</XunitAnalyzersPackageVersion> | |||
<XunitPackageVersion>2.3.1</XunitPackageVersion> | |||
<XunitRunnerVisualStudioPackageVersion>2.4.0</XunitRunnerVisualStudioPackageVersion> | |||
<XunitVersion>2.4.1</XunitVersion> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Odd. aspnet/Extensions is on 2.4.0
and that bumping things up here would cause different package downgrade errors. Glad it doesn't.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we move aspnet/Extensions to Xunit
2.4.1
and (then) the other repos?
Yes, but I would do it in reverse order. Move AspNetCore to 2.4.1, then Extensions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Move AspNetCore to 2.4.1, then Extensions
In release/3.0-preview3
or master
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
master. It's not urgent for preview3
…dotnet/razor#238) * Update dependencies * Add workaround for dotnet/sdkdotnet/aspnetcore-tooling#2976 * Remove unused NETStandard package version variable and overrides * Update xunit to 2.4.1 \n\nCommit migrated from dotnet/razor@6708297
…dotnet/razor#238) * Update dependencies * Add workaround for dotnet/sdkdotnet/aspnetcore-tooling#2976 * Remove unused NETStandard package version variable and overrides * Update xunit to 2.4.1 \n\nCommit migrated from dotnet/razor@6708297 Commit migrated from dotnet/aspnetcore@61e85256a653