Skip to content
This repository has been archived by the owner on Dec 25, 2023. It is now read-only.

Multi-Target .NET Core 3.1, 5 & 6 instead of .NET Standard 2.0 #189

Closed
pascalberger opened this issue May 3, 2022 · 0 comments · Fixed by #195
Closed

Multi-Target .NET Core 3.1, 5 & 6 instead of .NET Standard 2.0 #189

pascalberger opened this issue May 3, 2022 · 0 comments · Fixed by #195
Labels
Breaking change
Milestone
2.0.0

Comments

@pascalberger
Copy link
Member

Since Cake 2.0 has dropped support for .NET Framework and .NET Core < 3.1, we should also follow best-practices and multi-target .NET Core 3.1, 5 & 6
@pascalberger pascalberger added this to the 2.0.0 milestone May 3, 2022
pascalberger added a commit that referenced this issue Jul 23, 2022
@pascalberger
(GH-189) Multi-Target .NET Core 3.1, 5 & 6 instead of .NET Standard 2.0
9d59bf9
@pascalberger pascalberger mentioned this issue Jul 23, 2022
Merged
pascalberger added a commit that referenced this issue Jul 23, 2022
@pascalberger
(GH-189) Multi-Target .NET Core 3.1, 5 & 6 instead of .NET Standard 2…
627b677 
….0 (#195)
@pascalberger pascalberger changed the title Multi-Target .NET Core 3.1, 5 & 6 instead of .NET Standard 2.0 #249 Multi-Target .NET Core 3.1, 5 & 6 instead of .NET Standard 2.0 Dec 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Breaking change
Projects
None yet
Milestone
2.0.0
1 participant
@pascalberger