Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Update classlib tempalte to include .NET Standard 2.1

See original GitHub issue

Running

dotnet new classlib

Should still create a .NET Standard 2.0 project. However, it should be possible for a developer to specify the 2.1 TFM as well:

dotnet new classlib -f netstandard2.1

Since they are hardcoded in the template itself, we need to add it to the list.

Issue Analytics

State:
Created 5 years ago
Comments:8 (8 by maintainers)

Top GitHub Comments

1reaction

livarcocccommented, Mar 16, 2019

Re-activating since we had to pull this out due to the default in VS changing to netstandard2.1.

We need the option to create a netstandard 2.1 project, however, the default should continue being netstandard2.0 for both Visual Studio and the CLI.

cc @terrajobst

0reactions

vijayrkncommented, Mar 19, 2019

@mlorbetske - How much work is involved in adding this feature?

Mike showed me where to make the change. Have a PR with the fix.

Top Results From Across the Web

Tutorial: Create a .NET class library using Visual Studio

On the Add a new project page, enter library in the search box. Choose C# or Visual Basic from the Language list, and...

c# - How can I change a .NET standard library to ...

Open up the project file (.csproj) and change the TargetFramework to net462 <PropertyGroup> <TargetFramework>net462</TargetFramework> ...

NET Core 3 - .NET Standard 2.1

.NET Core 3.0 implements .NET Standard 2.1. However, the default dotnet new classlib template generates a project that still targets .NET Standard 2.0....

Upgrading an older .NET SDK to .NET Core and .NET Standard

LIVE: Upgrading an older .NET SDK to .NET Core and . NET Standard. 19K views · Streamed 4 years ago ...more ...

Creating your first shared library in .NET Core - DevTrends

Sharing libraries between projects is a fundamental requirement in all but the most simple applications. This post looks at how things have changed...