Shulou(Shulou.com)06/01 Report--

This article will explain in detail which kind of Class Library should be configured in Visual Studio 2015 and 2017. The content of the article is of high quality, so the editor will share it with you for reference. I hope you will have a certain understanding of the relevant knowledge after reading this article.

Microsoft is sometimes an unreasonable paternalism. One example is that it has a lot of Class Library templates that ordinary people can't understand in Visual Studio 2015 and 2017.

Do you really know which one to choose?

This is the long list that you may be familiar with in VS2017 (and because I don't have a UWP development project installed, this table is incomplete). In fact, after careful study, it is not so terrible, they actually have only two types.

Platform-related Class Library

Since the .NET Framework 1.0, the type Class Library (.NET Framework) has existed. So with your eyes closed, you know that this type of project can only be used for .NET Framework projects. With this basic understanding, you will also know that templates such as iOS, tvOS, watchOS, Android and UWP are also platform-related and can only be used by projects on the same platform.

Although the project generated by such a template cannot be used across platforms, it is still a good way to reasonably divide the granularity of the project, resulting in high aggregation within each Class Library and low coupling between other projects.

Class Library that can be used across platforms

Class Library (Portable) is the cross-platform Class Library solution that Microsoft first thought of, which is generally called PCL. Because of the limitations in its actual use, Microsoft no longer recommends it.

The new solution to replace PCL is Class Library (. NET Standard). This type of engineering allows developers to use a larger collection of API than PCL. You may still need some practice to understand, but now simply memorize the answer, "if you need to develop cross-platform projects, this template is what you need."

Of course, there are a few special cases that need to be specified,. NET Core and Xamarin.Forms.

Projects created by Class Library (.NET Core) templates can only be used by other .NET Core projects. This is, of course, the same as other platform-related Class Library templates. But the .NET Core is a special platform that can run on multiple operating systems (which gives rise to another cross-platform). The .NET Core's cross-"platform" means that it spans multiple operating systems (Windows/Mac/Linux). The cross-platform of the .NET Standard means that it can be referenced by projects on multiple platforms (.NET Framework/.NET Core/Mono/Xamarin/Unity).

Class Library (Xamarin.Forms) is also quite special. First of all, it is temporarily a PCL-based template and should be upgraded to a .NET Standard-based template in the future. Second, the project that can reference it, the current limit is Xamarin-related projects, and other project types may be added in the future.

On Visual Studio 2015 and 2017 to configure which kind of Class Library to share here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.