Remove Support for Older Versions of .NET Framework #33
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When Capstone.NET 2.0 was first released, .NET Core did not support Windows GUI applications. As such, Capstone.NET 2.0 explicitly supported .NET Framework 4.0 and greater to allow developers building Windows GUI applications to use Capstone.NET.
Today, Windows GUI applications are supported on .NET. Developers no longer need to use .NET Framework to build Windows GUI applications. Furthermore, Microsoft has deprecated, and no longer supports, any version of .NET Framework before .NET Framework 4.6.2.
Starting with Capstone.NET 2.1, the minimal supported version of .NET Framework is .NET Framework 4.6.1. If you're wondering why .NET Framework 4.6.1 even though it is deprecated, please consult the .NET Compatibility Matrix.