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

[Feature]: Move Search Service from .NET Core 3.1 to .NET 6 #9149

Closed
joelverhagen opened this issue Jun 21, 2022 · 1 comment
Closed

[Feature]: Move Search Service from .NET Core 3.1 to .NET 6 #9149

joelverhagen opened this issue Jun 21, 2022 · 1 comment
Assignees
Labels
feature-request Customer feature request

Comments

@joelverhagen
Copy link
Member

Related Problem

No response

The Elevator Pitch

.NET Core 3.1 is EOL on December 13, 2022.
https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core

We should move the Search Service to .NET 6 before that time.

Additional Context and Details

No response

@joelverhagen joelverhagen added the feature-request Customer feature request label Jun 21, 2022
joelverhagen added a commit to NuGet/ServerCommon that referenced this issue Jul 15, 2022
joelverhagen added a commit to NuGet/NuGet.Jobs that referenced this issue Jul 18, 2022
1. Move to new build tools (from NuGet/ServerCommon#400)
2. Move the search web app and tests from .NET Core 3.1 to .NET 6. Only one small code change, for a deprecated API.
3. Move the data warehouse SQL project to .NET Framework 4.7.2 since VS 2022 no longer has a .NET 4.5 targeting pack. We need the VS 2022 agent to build .NET 6.

Progress on NuGet/NuGetGallery#9149
@joelverhagen joelverhagen self-assigned this Aug 23, 2022
@joelverhagen
Copy link
Member Author

This is fully deployed to PROD.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Customer feature request
Projects
None yet
Development

No branches or pull requests

1 participant