Release 4.0 breaks build of all projects targeting min-version <4.72
See original GitHub issueThis was a totally useless change, it has no effect except annoying our patrons.
It does not improve anything, it has absolutely no effect on the weavers and their dependencies, because they run in the context of Visual Studio/MSBuild (which btw. only guarantees .net46, see excerpt of MSBuild.exe.config
)
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.6" />
</startup>
The target version only specifies the minimum version this code is compatible with, it does not enforce anything.
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
Your project is not referencing the ".NETFramework ...
I had a similiar issue when upgrading some projects from 4.6.2 to 4.7.2 - this happened for both our ASP.Net Core solution targetting...
Read more >Retargeting Changes for Migration from .NET Framework ...
All .NET applications targeting the .NET Framework version 4.7.2 or higher use the native implementation.This change might result in some ...
Read more >Can we have multiple target versions v4.7.2
Due to third party dependency we are planning to support .NET 4.8 and 4.7.2 framework into application. <TargetFrameworkVersion>v4.7.2 ...
Read more >How to Update 70 Projects to .Net 4.8 With Ease?
Net 4.7.2 and there are no breaking changes. ... We can select the projects we want to upgrade and choose the target version:....
Read more >Bulk Updating .NET Framework Versions In Legacy ...
For one of our customers, I recently had to change the target .NET Framework version from 4.5.1 to 4.6.1 because a new version...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@SimonCropp @ltrzesniewski I would recommend reverting the latest changes and unlist 4.0 from nuget.
This work has to also happen with Fody. You / your community knows your projects the best and audience usage patterns. I’m flagging the CVE