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.

dotnet pack does not produce package on net core 2.0.0 web project

See original GitHub issue

Steps to reproduce

Install net core 2.0.0 sdk Create a basic Web project with net461 target framework and referencing AspNetCore 2.0.0 Execute the dotnet pack myproject.csproj

Expected behavior

A nupkg is generated

Actual behavior

nothing is produced. Before I migrate to 2.0.0, packages were normally produced locally and with TFS builds

Environment data

dotnet --info output: Product Information: Version: 2.0.0 Commit SHA-1 hash: cdcd1928c9

Runtime Environment: OS Name: Windows OS Version: 6.1.7601 OS Platform: Windows RID: win7-x64 Base Path: C:\Program Files\dotnet\sdk\2.0.0\

Microsoft .NET Core Shared Framework Host

Version : 2.0.0 Build : e8b8861ac7faf042c87a5c2f9f2d04c98b69f28d

Issue Analytics

State:
Created 6 years ago
Comments:18 (8 by maintainers)

Top GitHub Comments

69reactions

dasMullicommented, Aug 28, 2017

Web projects are now marked as not packable by default. You can change that by adding the following property to the csproj:

  <PropertyGroup>
    <IsPackable>true</IsPackable>
  </PropertyGroup>

13reactions

nguerreracommented, Aug 29, 2017

I completely agree that pack shouldn’t silently do nothing when IsPackable=false. I suggest logging an issue on https://github.com/nuget/home. cc @rohit21agrawal