[GH-ISSUE #20] .net6+ #17

Closed
opened 2026-02-26 01:35:47 +03:00 by kerem · 4 comments
Owner

Originally created by @mph911 on GitHub (Mar 23, 2022).
Original GitHub issue: https://github.com/junian/Standard.Licensing/issues/20

Is there any plan to port to .net6+?

Originally created by @mph911 on GitHub (Mar 23, 2022). Original GitHub issue: https://github.com/junian/Standard.Licensing/issues/20 Is there any plan to port to .net6+?
kerem closed this issue 2026-02-26 01:35:47 +03:00
Author
Owner

@CraigRichards commented on GitHub (Oct 8, 2022):

The .NetStandard 2.0 target framework would cover your .Net6 requirement.

<!-- gh-comment-id:1272226408 --> @CraigRichards commented on GitHub (Oct 8, 2022): The .NetStandard 2.0 target framework would cover your .Net6 requirement.
Author
Owner

@AntiGuideAkquinet commented on GitHub (Feb 24, 2023):

I believe a change of targeted frameworks would be sensible altough not necessary to use the library in .NET 6.

As suggested here a switch to support netstandard2.0 (and net461 explicity) would bring us in line with other widespread librarys and allow usage of a few new features.

That means dropping following targets:

  • net45
  • net40
  • portable-net45+win8+wpa81+wp8
  • portable-net403+sl50+win8+wp8

And keeping/adding:

  • netstandard2.0
  • net461

From the linked page:

.NET Standard 1.x is distributed as a granular set of NuGet packages, which creates a large package dependency graph and results in developers downloading a lot of packages when building. Modern .NET implementations support .NET Standard 2.0. You should only target .NET Standard 1.x if you specifically need to target an older platform.

<!-- gh-comment-id:1443382507 --> @AntiGuideAkquinet commented on GitHub (Feb 24, 2023): I believe a change of targeted frameworks would be sensible altough not necessary to use the library in .NET 6. As suggested [here](https://learn.microsoft.com/en-us/dotnet/standard/library-guidance/cross-platform-targeting#older-targets) a switch to support `netstandard2.0` (and `net461` explicity) would bring us in line with other widespread librarys and allow usage of a few new features. That means dropping following targets: - `net45` - `net40` - `portable-net45+win8+wpa81+wp8` - `portable-net403+sl50+win8+wp8` And keeping/adding: - `netstandard2.0` - `net461` From the linked page: > .NET Standard 1.x is distributed as a granular set of NuGet packages, which creates a large package dependency graph and results in developers downloading a lot of packages when building. Modern .NET implementations support .NET Standard 2.0. You should only target .NET Standard 1.x if you specifically need to target an older platform.
Author
Owner

@mzayarnyuk commented on GitHub (Mar 16, 2023):

yes pls add separated targeting;
no one ask to remove standard2.0 etc because someone use that in old projects;
but add new separated targeting make easy to use who want built with own src; and make better perfomance and iluminate aoutdated standard and other old refs that not needed if use in modern net6-7 or maui etc

<!-- gh-comment-id:1471777913 --> @mzayarnyuk commented on GitHub (Mar 16, 2023): yes pls add separated targeting; no one ask to remove standard2.0 etc because someone use that in old projects; but add new separated targeting make easy to use who want built with own src; and make better perfomance and iluminate aoutdated standard and other old refs that not needed if use in modern net6-7 or maui etc
Author
Owner

@mzayarnyuk commented on GitHub (Mar 16, 2023):

is really critical for you, in other way mans will check and choose some new - more bad maybe - but simple implementation that easy to try and integrate with there apps;

<!-- gh-comment-id:1471782636 --> @mzayarnyuk commented on GitHub (Mar 16, 2023): is really critical for you, in other way mans will check and choose some new - more bad maybe - but simple implementation that easy to try and integrate with there apps;
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Standard.Licensing#17
No description provided.