Supported frameworks not always populated correctly
See original GitHub issueFor Newtonsoft.Json
(for example), this line of code seems to ignore all frameworks if one of them is null, instead of just skipping the null one and adding all others. So that means this data is not in the database…
Note that this was by design, but it makes no sense.
Please fix (fairly trivial) and reflow all packages that have no supported frameworks data in the database.
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Cannot Change Target Framework?
A modern class library should use multiple target frameworks today, which means the options can only be set in project files right now,...
Read more >dotnet restore unable to resolve .NET Framework libraries ...
It works in Visual Studio but not when using the dotnet CLI. My class library targets .NET 4.6.1. Error: "Unable to resolve 'MyCompany....
Read more >Runtime Changes for Migration from .NET Framework 4.5 ...
Beginning in the .NET Framework 4.5.1, the .NET Framework will attempt to automatically reconnect broken SQL connections.
Read more >A Guide to SAMHSA's Strategic Prevention Framework
No community can address all of these factors—at least not all at once . So, the first step in developing a prevention plan...
Read more >Test Automation Frameworks
See how testing frameworks can improve the efficacy and efficiency of any automated testing process. Learn more about the most common types of...
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 FreeTop 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
Top GitHub Comments
I am fine with either approach. For the first one it would be best to run when we have the least load on our servers ensuring that it doesn’t result in cascading index lag. To be safe I think it would be better to go with the second approach.
verified