There’s a problem to your approach: .NET Standard is the most bare-bones implementation of .NET available, meaning that only basic features which are platform- and scenario-agnostic are implemented. HttpContext exists on both the .NET Framework and .NET Core (both of which implement .NET Standard, by the way), but being specific to the Web, it does … Read more
You haven’t done anything wrong, this is expected to happen. If you want nothing more than your own DLL being added to a new .NET Framework project, you have to target .NET Standard 2.0 for your library wait for a .NET Framework version that natively supports both the API and assembly versions – which is … Read more
I’ve added a repo that shows you how to do this. From the README.md: Requirements Generally speaking, using libraries targeting .NET Standard in an application targeting .NET Framework requires the application project to include a NuGet reference for .NET Standard (NETStandard.Library). This ensures that the right set of assemblies are included with the application. In … Read more
Referencing .NET Standard 2.0 packages is supported using the following: NuGet 3.6.0 or higher for VS 2015 (from NuGet’s download site – may not yet be listed as recommended latest) Install the “.NET Standard Support for Visual Studio 2015” from https://aka.ms/netstandard-build-support-netfx (NuGet in VS will also print a link to this in its output window). … Read more
As trite as it sounds, try rebuilding then restarting VS – and get on with your day 🙂
I will try to further clarify your doubts and extend Jon Skeet answer. .NET Standard is a specification, so a library compiled for a specific .NET Standard version can be used in different .NET Standard implementations. As said in my other comment, a good analogy for the relationship between .NET Standard and other .NET Standard … Read more
Transitive project references (ProjectReference) Transitive project references are new feature of SDK-style csproj (1,2) format used in .NET Core/.NET >= 5. You can also use this csproj for old .NET Framework projects (1,2,3) but with some exceptions. In this SDK-style format project references (represented by <ProjectReference> entry in .csproj file) are transitive. This is different … Read more
Update: The name changed to “.NET Embedding” and it is at v0.4 at the time of this update. https://developer.xamarin.com/releases/dotnetembedding/dotnetembedding_0/dotnetembedding_0.4/ New instructions: Installing .NET Embedding Original post: You can use Mono’s Embeddinator-4000 It supports various language consumers, so it surfaces .NET code as idiomatic code in the target language. This is the list of supported languages … Read more
Binding redirects are a .NET framework concept, there are no binding redirects on .NET Standard and .NET Core. However, an application (the actual .NET Framework or .NET Core application) need to resolve the files to be used. On .NET Core, this is done by generating a deps.json file based on the build input and a … Read more
It’s not about the CLR, it’s about the sandbox. System.Drawing relies heavily on GDI/GDI+ to do its thing. Because of the somewhat risky nature of those APIs (large attack surface) they are restricted in the App Service sandbox. Win32k.sys (User32/GDI32) Restrictions For the sake of radical attack surface area reduction, the sandbox prevents almost all … Read more