Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support for previous .NET framework versions?
See original GitHub issueBased on the AppVeyor build configuration file, Puppeteer Sharp seems to only support .NET 4.7.1 (and .NET Core 2.0).
Based on the .nuspec file inside the NuGet package (downloaded directly from NuGet Gallery), the package targets .NET Standard 2.0.
Are you open to supporting other versions? I wanted to use this project in a solution for which all-but-one project targeted .NET 4.0. But I also didn’t have any problems updating the projects to target 4.7.1.
Also, is there a reason why the AppVeyor build configuration runs tests again net471 and netcoreapp2.0 but the NuGet package is created targeting ".NETStandard2.0"? They don’t seem (necessarily) equivalent based on this:
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Puppeteer-Sharp is a multi-platform .NET standard 2.0 library. That means it can be used on any .NET Runtime compatible with 2.0, .NET Framework 4.6.1+ or .NET Core 2.0+.
AppVeyor runs our unit tests, which is a multi-target library. It runs in .NET 4.7.1 and .NET Core 2.0 with the only purpose of testing the multi-platform ability of Puppeteer-Sharp. Because .NET Standard guarantees same API but not same behavior (see #90). Remember, those are the Tests’ targets, not the library itself.
So, going back to versions. Puppeteer Sharp is a .NET standard library, so that means .NET 4.5+. And there is no way we can remove the .NET Standard from the equation, because it’s our bridge between .NET Framework and in .NET Core.
Being said that. If you want to see if it is possible to make it multi-target .NET Standard 2.0 and .NET Framework 4.0, using the same code and running the same tests, we could take your Pull Request into consideration. But it’s not one of my motivations right now.
@kblok I’d like to +1 the idea of adding separate support for non .net-standard projects. I have some older projects I’d like to use this library on that aren’t upgraded. The one I’m working on now is 4.5 and I’m not certain how much effort it would take to upgrade to 4.6.1 or higher.