Westwind.Utilities is a really old project that I've been using since the very early years of. Using a single project I can create binaries - and a NuGet package if desired - for multiple platforms. NET library project that can target multiple. Multi-targeting from a single project is an awesome feature that makes it possible to create a single. To really put this all into perspective I decided to move one of my libraries - Westwind.Utilities - to.
In this post I'll talk about full framework. NET Standard 2.0 in your class libraries (or applications) and can have a very reasonable expectation of interoperability for a number of platforms. The key takeaway for this post is that your. NET Again for a more detailed discussion on just how that works. NET Standard works here, but you can read my earlier blog post. I don't want to rehash all the details about how. NET Standard for a class library is also what gives the new SDK project type that is required to make multi-targeting work. NET Standard is that it provides a common interface to consumers of a library, as well as an official guideline to the actual runtime implementers.įor Visual Studio purposes targeting. NET Standard 2.0 I can insure that my DLL will run on any of the target platforms that. NET 4.6.1, Xamarin, Mono, UWP and Unity all of which will eventually support. NET Standard 2.0 compliant DLL it will run on. NET Standard 2.0 which means that if I implement a. NET Standard APIs to the actual underlying APIs on the specific runtime.įor the purposes of this discussion, the salient point is that.
NET Standard forwarding assemblies that map the. The logistics of this involve some runtime magic where each runtime provides a set of. NET Standard is a standard not an implementation and it's up to the runtime to implement the features set forth in the standard. The standard specifies what base features the runtime has to implement to support it.NET Standard describes the base API library - what we used to think of as the Base Class Library (BCL) in full framework that make up the core features of the platform. NET Standard is a specification that serves as a blue print for. NET Core 2.0.įor those of you that don't know.
NET Core payload for a lightish install, and the install is side by side with Visual Studio 2017 RTM so both work.NET Standard?Ī key concept to the porting process is. NET Core 2.0/.NET Standard 2.0 in the release version of Visual Studio, and that's why the Preview install is required. Note that currently there's no support for.
Visual Studio 2017 Update 3 Preview 2 or later.The porting process was even easier than I expected, although the tooling required a bit of patience to get on with. NET Core 2.0 and multi-targeting the project to support. In this post I describe porting an existing full framework library to. NET Core 2.0 will change all that by making it possible for most libraries to be ported with minimal effort. NET Core 1.x it's been hit or miss feature wise to feel confident you can actually make it through a project without getting stuck with some missing core feature you can't easily find and have to build from scratch. NET Core and providing the full featured eco-system that we've come to expect from. This isn't just important to me personally, but I think this is a vital requirement for moving much of the support libraries that exist for.
NET Core 2.0 it really looks like most code will migrate pretty easily. Nobody wants to rewrite code they already have just to get back to square one, but with. NET Core is actually pretty important factor to overcoming my reluctance to move into. Being able to bring some of the tools I use to be productive over to. NET Core really has been a deciding factor for me to start moving some of my existing full framework libraries that I've been using for as long as I have been using. NET Core 2.0 with their much bigger base library foot print and the real possibility of porting the majority of existing library code over to.
In fact, to date I have yet to build anything 'real' for customers beyond a few internal infrastructure projects and quite a few sample applications.įor me personally. NET Core have been on my mind for a long time now - years really, but the reality is while I've been using the technology quite a bit, I've not jumped in with both feet.