dotnet pack does not produce nupkg for webapi project

Steps to reproduce

dotnet new webapi dotnet pack

Expected behavior

nupkg should be generated for project

Actual behavior

build succeeds, but nupkg is not generated for project

Environment data

dotnet --info output:

.NET Command Line Tools (2.0.0)

Product Information: Version: 2.0.0 Commit SHA-1 hash: cdcd1928c9

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

Microsoft .NET Core Shared Framework Host

Version : 2.0.0 Build : e8b8861ac7faf042c87a5c2f9f2d04c98b69f28d

[dasMulli]

I was referring to this document: https://octopus.com/docs/guides/deploying-asp.net-core-web-applications

# Publish the application to a folder
dotnet publish source/MyApp.Web --output published-app --configuration Release

# Package the folder into a ZIP
octo pack --id MyApp.Web --version 1.0.0 --basePath published-app 

Problem is that ASP.NET Core applications need a special handling here (in contrast to e.g. a .NET Core console application). Also, you would want MVC precompilation to be performed which is only done during publish.

It may be beneficial to follow up with octopus deploy on their recommendations and documentation.

[srini89]

@KellyR-STCU : thanks for the response .So we are not able to do with Nuget packages ?

I am pretty new to this tool can give me some idea how did you use octopack.exe and dotnet publish on the same agent? and did we unzip in octopus deploy to open the files on IIS?