NuGet: support .NET Core & .NET Standards
See original GitHub issueThe OpenGL.Net_VC15 solution includes project targeting .NET Core 1.1, .NET Core 2.0 and .NET Standard 2.0. The assemblies should be included in the NuGet package.
- Determine side effects for other derived NuGet packages (mainly .CoreProfile, .ES2Profile)
- Change .appveyor in order to use Visual Studio 2017 image (version 15.3)
- Determine .NET Standard 1.1 limitations
- Cannot have library search path (multi-platform ANGLE support broken)
Memory.Set
thrownNotImplementedException
- Determine .NET Standard 1.4 limitations
- Cannot have library search path (multi-platform ANGLE support broken)
Memory.Set
thrownNotImplementedException
- Determine .NET Standard 2.0 limitations
Memory.Set
thrownNotImplementedException
- Determine .NET Core App 1.1 limitations
- Cannot have library search path (multi-platform ANGLE support broken)
Memory.Set
thrownNotImplementedException
- Generic overrides cause boxing of blittable types (lack of
__makeref
) - Logging is not supported by metadata (lack of
System.Xml
) - No support for experimental GL extensions
- EGL initialization depends on current working directory instead of assembly directory
- Determine .NET Core App 2.0 limitations
- No support for experimental GL extensions
- EGL initialization depends on current working directory instead of assembly directory
Issue Analytics
- State:
- Created 6 years ago
- Comments:12 (5 by maintainers)
Top Results From Across the Web
NET Standard
NET Standard 1.x is distributed as a granular set of NuGet packages, which creates a large package dependency graph and results in developers ......
Read more >If a nuget Package is .Net Standard 2.0 supported then can ...
1 Answer 1 ... As this document indicates that: Net Standard 2.0 supports >= Net Core 2.0 . Net standard itself is compatible...
Read more >Please stop lying about .NET Standard 2.0 support!
In this post I described how some NuGet packages that support . NET Standard 2.0, don't support . NET Core 2.1/. NET Core...
Read more >If I want to create a NuGet package, should I write it in .NET ...
If I want to create a NuGet package, should I write it in .NET Standard, .NET Core, or .NET Framework? I'm writing a...
Read more >When writing .Net Standard projects, is it OK to include ...
When developing a .NET Standard library, it is ok to add other NuGet package dependencies as long as they provide an assembly which...
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
@luca-piccioni hey is there a reason why 0.7.1 NuGet package have .NET Core binaries, but 0.8.4 haven’t? Sorry but I can’t find any corresponding discussion.
Indeed we have a nuget package with .NET Core binaries,versioned as 0.7.1.