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

[Question]: Should V6 only support "MS Supported" Net Frameworks ? #290

Closed
Smurf-IV opened this issue Aug 24, 2021 · 8 comments
Closed

[Question]: Should V6 only support "MS Supported" Net Frameworks ? #290

Smurf-IV opened this issue Aug 24, 2021 · 8 comments
Labels
answered This question has been adequately answered. in progress A fix for this issue is in the works. question Further information is requested

Comments

@Smurf-IV
Copy link
Member

In order to allow the suite to move into the latest "Fonts", PInvokes, "Remove MissingFramework API's", Winform structures / etc.
Can V6 only support MS Net Frameworks that it will cover in its lifetime?
:
https://dotnet.microsoft.com/platform/support/policy/dotnet-framework

i.e. only .Net 4.6.2 onwards.

@Smurf-IV Smurf-IV added the question Further information is requested label Aug 24, 2021
@PWagner1
Copy link
Contributor

So drop support anything below 4.6.2?

@PWagner1
Copy link
Contributor

I'd say yes

@PWagner1 PWagner1 added the answered This question has been adequately answered. label Aug 24, 2021
@PWagner1 PWagner1 added this to the November 2021 (Version 6) milestone Aug 24, 2021
@Smurf-IV
Copy link
Member Author

I have assigned to you to modify the build scripts (And TFM support)
And then assign back to me if you want me to go through and delete the "MissingFrameworks API's" or <net 462 #defines

@PWagner1 PWagner1 added the in progress A fix for this issue is in the works. label Aug 24, 2021
PWagner1 added a commit that referenced this issue Aug 24, 2021
@PWagner1
Copy link
Contributor

@Smurf-IV Back over to you, I've done the edits on alpha-enh#290

image

image

@PWagner1 PWagner1 assigned Smurf-IV and unassigned PWagner1 Aug 24, 2021
@PWagner1
Copy link
Contributor

@Smurf-IV Just a thought, since we're dropping support for below 4.6.2, should we also ditch the lite packages? I'll also mirror changes on the Extended-Toolkit.

@Smurf-IV
Copy link
Member Author

@Smurf-IV Just a thought, since we're dropping support for below 4.6.2, should we also ditch the lite packages?

That'll make the explanation text easier (i.e. it doesn't need it any more :-))
Description can then state something like "An update .... supporting MS Supported Net Winform Frameworks from .Net4.62 (inc) onwards"

@PWagner1
Copy link
Contributor

@Smurf-IV Just a thought, since we're dropping support for below 4.6.2, should we also ditch the lite packages?

That'll make the explanation text easier (i.e. it doesn't need it any more :-))
Description can then state something like "An update .... supporting MS Supported Net Winform Frameworks from .Net4.62 (inc) onwards"

Also it'll make building Extended-Toolkit a heck of a lot easier! :)

Smurf-IV added a commit that referenced this issue Aug 24, 2021
- Remove API Manipulation to support TFM below 462
- Fix Fallout from API removal
- Fix a few Compiler warning messages
Implements #290
@Smurf-IV
Copy link
Member Author

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
answered This question has been adequately answered. in progress A fix for this issue is in the works. question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants