NETStandard packages and you don’t even know it!
You are likely these days to be referencing. Our own StackifyLib package for sending application errors, logs, and metrics to our platform has been converted. Common libraries like JSON.NET, log4net, NLog, Dapper, Entity Framework and many others now support it. Most popular 3rd party libraries have all switched to the new. This is what enables the cross-platform capabilities. NET Core, we now reference packages based on the. NET code has been written with .NET 4.5 and basic assembly references or NuGet packages. NETStandard packagesįor the last few years, all. You effectively have 2 options now when creating a Windows Service: NET Framework. The good news is you can mix. Windows Services only work with the full.
NET Core framework there is tiny trade-offs and differences here and there based on Windows vs Linux. For example, Windows registry, WMI, Microsoft specific cryptography APIs, and… Windows Services are some quick examples. Anything too OS specific is not supported. This requires a unified surface area of APIs.
NET Core is the portability of your code across multiple types of apps and operating systems. NET Core Does Not Like Windows Specific “Stuff”
