question-mark
Stuck on an issue?

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.

NuGet: support .NET Core & .NET Standards

See original GitHub issue

The 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 thrown NotImplementedException
  • Determine .NET Standard 1.4 limitations
    • Cannot have library search path (multi-platform ANGLE support broken)
    • Memory.Set thrown NotImplementedException
  • Determine .NET Standard 2.0 limitations
    • Memory.Set thrown NotImplementedException
  • Determine .NET Core App 1.1 limitations
    • Cannot have library search path (multi-platform ANGLE support broken)
    • Memory.Set thrown NotImplementedException
    • 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:open
  • Created 6 years ago
  • Comments:12 (5 by maintainers)

github_iconTop GitHub Comments

3reactions
ForNeVeRcommented, Jul 20, 2019

@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.

2reactions
luca-piccionicommented, Dec 15, 2017

Indeed we have a nuget package with .NET Core binaries,versioned as 0.7.1.

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found