.net standard 2.0 templates in visual studio for mac

.Net Standard 2.0 Templates In Visual Studio Portable Right Now

Ive been bitten by this recently when attempting to multi-target different framework versions, and creating a unit test project.

.Net Standard 2.0 Templates In Visual Studio Portable Right Now

Most are not actually portable right now:).NETCore is not done by a long shot, probably takes another two years at the clip they are going.

Also we regularly see ASP associated with.Net Core.

This is also very confusing.

On the other hand, libraries that target.NET Core can only run on the.NET Core runtime.

Thats important, for instance, to make unit test class libraries runnable.

Any platform that implements a.NET Standard is compatible with libraries that target that.NET Standard.

One of those compatible platforms is.NET Core.

Conversely, the.NET Core library templates exist to access more API surface area (at the expense of compatibility) and to specify a platform against which to build an executable.

TL;DR; In the past, class libraries targeted the full framework, which includes an application model.

Ive intentionally kept my answer scoped to the original question.

As pictures are worth a thousand words, the following will make things very clear.

This unifies the.NET platforms and prevents future fragmentation.

A situation which was catered for given that many have want to reuse existing libraries written thein full.Net Framework with no interest for cross-platform benefits (OS-level and App-Model level).If you still feel Im wrong, perhaps you can argue with Microsoft, who authored those images.:-).

It is written as a library that targets.NET Standard, therefore you can use it everywhere you can use.NET Standard.

Yes, they made a mistake in that image.

IDog.NetFramework (Specific oldest and has the most features).

An app written for.NET Standard 1.0 should be able to compile and run with any version of Framework, Core, Mono, etc., that advertises support for the.NET Standard 1.0 collection of libraries.

Similar is true for.NET Standard 1.1, 1.5, 1.6, 2.0, etc.

As long as the runtime provides support for the version of Standard targeted by your program, your program should run there.

This doesnt mean you cant take dependencies on other assemblies, or APIs published by other vendors (i.e.: items on NuGet).

But it does mean that any dependencies you take must also include support for your version of.NET Standard..NET Standard is evolving quickly, but its still new enough, and cares enough about some of the smaller runtime profiles, that this limitation can feel stifling.

Note a year and a half later: this is starting to change, and recent.NET Standard versions are much nicer and more full-featured).

For a class library project looking for wide distribution, thats an attractive promise.

For a class library project used mainly for internal purposes, it may not be as much of a concern.

All we can do here is give you info about the products, so you can be informed for making your own decision.

This is specially useful in ASP.NET Core applications, since you can now host ASP.NET on Linux (cheaper hosting prices).

Now, since.NET Core was open sourced, its technically possible to develop libraries for other platforms.

But since there arent frameworks that support it, I dont think thats a good idea.

Its also possible to target web clients with the UNO platform and Blazor (although both are kind of experimental right now).

For example, I developed a point of sale application that had the following architecture.

.Net Standard 2.0 Templates In Visual Studio For Mac