Menu
I would like to use the latest .NET Core in a new Universal Windows Class Library.
However creating a new library in VS2015 the System.Net.Sockets.Socket API does not appear to be updated. In particular I want this commit: https://github.com/dotnet/corefx/pull/4079/files
My project.json looks like:
{
"dependencies": {
"Microsoft.NETCore.UniversalWindowsPlatform": "5.0.0"
},
"frameworks": {
"uap10.0": {}
},
"runtimes": {
"win10-arm": {},
"win10-arm-aot": {},
"win10-x86": {},
"win10-x86-aot": {},
"win10-x64": {},
"win10-x64-aot": {}
}
}
345
The user can use the “dotnet new classlib” or dotnet new “Class Library” command from the dotnet-CLI toolset to create a new dotnet core class library project also known as Dynamic Link Library or DLL. The command provides few options that can be applied as a parameter to tweak the output of the command, like for example ...
To use a library across .net framework or core, you can develop the library in .net standard, then you can use this for both.
With the UWP, the .NET Core is included as a set of NuGet packages in your app. When you create a new project, you’ll see only the general Microsoft.NETCore.UniversalWindowsPlatform package dependency, but if you look at this package on NuGet, you’ll see all of the .NET Framework libraries that are included, as shown in Figure 1.
Finally, .NET Core is the underlying framework on which .NET Native depends. When .NET Native was designed, it was clear that the .NET Framework wouldn’t be suitable as the foundation for the framework class libraries.
You could try upgrading that package using their nightly feed: https://dotnet.myget.org/gallery/dotnet-core
136
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
