Why create a class library (package)?

Question

I've been creating class libraries for years and they have always met my needs.

Now when I went to create a class library, Visual Studio is promoting a new component called Class Library (Package). It's front and center, as if it's the default now. The regular Class Library is now buried and much harder to find.

I am biased toward familiar things that are tried and true, but I want to keep up with the times.

Are there any advantages to using Class Library (Package)?

I'm in a corporate environment under a non-disclosure agreement. Whatever I create I don't think it can be open source, if that matters.

Answer 1

You can continue to use Class Libraries as you have however I'd recommend always staying current with the stack and platform. One way you could do that could be the ASP.NET Community Standup which is informative and fun. The new Class Library (Package) is part of vNext also known as ASP.NET Core 1.0

In short, taken from the description, it is:

A project template for creating a class library as a NuGet package that can target any platform.

I'd recommend these links for further reading.

Why create an ASP.NET 5 Class Library project?

Benefits of ASP.NET 5 Class Library projects (.kproj) over Class Library projects (.csproj)