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.

Sign up for GitHub

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

Jump to bottom

.NET Core 3.1 end-of-life #3474

Closed
bwateratmsft opened this issue Dec 14, 2022 · 1 comment · Fixed by #3528
Closed

.NET Core 3.1 end-of-life #3474

bwateratmsft opened this issue Dec 14, 2022 · 1 comment · Fixed by #3528
Assignees
@MicroFish91
Milestone
1.10.0

Comments

@bwateratmsft
Copy link
Contributor

I'm not super familiar with all the features of the Functions extension, but with .NET Core 3.1's end-of-life being yesterday, we should remove any facilities for creating new projects like this (which #3472 does some of), and we can also remove any code that is in place specifically to support 3.1 and/or below. In addition, branding changes should be made since, after .NET Core 3.1, all versions are just called ".NET".

There may or may not be changes to still make after #3472, someone more familiar with the extension will have to look 😄
@bwateratmsft
Copy link
Contributor Author

ASP.NET is still called "ASP.NET Core".

@nturinski nturinski added this to the 1.10.0 milestone Dec 15, 2022
@MicroFish91 MicroFish91 self-assigned this Jan 5, 2023
@MicroFish91 MicroFish91 mentioned this issue Jan 25, 2023
Merged
@microsoft microsoft locked and limited conversation to collaborators Mar 14, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@MicroFish91 MicroFish91

Labels
None yet
Projects
None yet
Milestone
1.10.0
3 participants
@nturinski @bwateratmsft @MicroFish91