Skip to content

Change WebSocket project to target netcoreapp3.0 #4346

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

Merged
merged 1 commit into from
Dec 3, 2018

Conversation

Tratcher
Copy link
Member

@Tratcher Tratcher commented Dec 1, 2018

#3754
This only changes the WebSocket package. The tests and samples were already updated.

These aren't getting updated, correct?
Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore
Microsoft.Extensions.Diagnostics.HealthChecks.EntityFrameworkCore
Microsoft.Extensions.Diagnostics.HealthChecks.EntityFrameworkCore.Tests

@Tratcher Tratcher added this to the 3.0.0-preview2 milestone Dec 1, 2018
@Tratcher Tratcher self-assigned this Dec 1, 2018
Copy link
Member

@dougbu dougbu left a comment

Choose a reason for hiding this comment

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

This looks fine but why just update the one project?

@natemcmaster
Copy link
Contributor

Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore should be updated to netcoreapp3.0 since it will need to compile with FrameworkReference before we ship RTM (#4257)
Microsoft.Extensions.Diagnostics.HealthChecks.EntityFrameworkCore can stay netstandard.
Microsoft.Extensions.Diagnostics.HealthChecks.EntityFrameworkCore.Tests should update to test on netcoreapp3.0 + .net framework.

@Tratcher Tratcher force-pushed the tratcher/3/middleware branch from 57ff816 to 07a355a Compare December 1, 2018 00:26
@Tratcher
Copy link
Member Author

Tratcher commented Dec 1, 2018

Updated.

Copy link
Member

@dougbu dougbu left a comment

Choose a reason for hiding this comment

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

Mostly curious: Does the src/Middleware/WebSockets/samples/TestServer/TestServer.csproj project need to be a legacy .csproj forever?

@Tratcher
Copy link
Member Author

Tratcher commented Dec 1, 2018

Need? No, but it's a good reminder that it's using a completely different stack for interop testing.

@Tratcher Tratcher force-pushed the tratcher/3/middleware branch from 07a355a to c0381de Compare December 3, 2018 17:06
@Tratcher Tratcher merged commit c0381de into master Dec 3, 2018
@Tratcher Tratcher deleted the tratcher/3/middleware branch December 3, 2018 17:07
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.

3 participants