revert: mintarget is no longer 460 as 452 is still supported #1195
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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Revert of 9738872
What is the current behavior? (You can also link to an open issue here)
In #1184 I bumped the min supported framework from
NET45
toNET46
due to misunderstanding the support-life-cycle ofNET452
. It's cousins450/451
have been EOL'ed butNET452
will be around for quite some time to come.What is the new behavior (if this is a feature change)?
Reverts the changes in #1184 and lowers min framework to
NET452
This is important as the default framework used in Visual Studio 2015 when creating a class library is still
452
. Staying at460
would have resulted in friction for our users and a common source of github issues whereby the resolution would always be asking our users to retarget their unit test assemblies to460
Does this PR introduce a breaking change?
The
net460
retarget was never published to NuGet.org.Please check if the PR fulfills these requirements
Other information:
This reverts commit 9738872.