OctoPack | Creates Octopus-compatible NuGet packages

With the introduction of Roslyn Analyzers, analyzers (and any dependencies) are now added to your Visual Studio project - one analyzer I added included 64 dependant packages. These DLLs are then included in the primary output of the project. Some of these DLLs will also be used by the project, but many will just be used by the analyzers.

So if I created a deployment package using the Publish functionality (for a web site), or use some other build tool (e.g. OctoPack), all files (including all analyzers) from the primary output are included. My view is that you should only deploy code that is absolutely essential (i.e. minimize the attack surface).

A couple of questions:

1. How are people excluding analyzers from production installations especially if, for example, you are using the Publish function in Visual Studio.

2. If you build a install package manually (e.g. using WIX), how do you determine which DLLs to exclude from your project.

I just went through every project in the solution and upgraded from .NET Framework 4.6.1 => 4.7.2 and only one project cannot be loaded. When I try to reload the project, it throws this error:

I have a windows service that I need to pack into a nuget package with OctoPack, but I have to exclude a directory called "Config" and a few other config files (these are instance specific and this will be deployed to multiple instances.) However the files are always included no matter what I put in the nuspec file.

Project directory:

I have a WebApp that I am trying to deploy to Azure. My stack is:

TeamCity 9.1.6 Octopus 4.0.7

I had been having a problem targeting the Staging slot which I can now do. However the Nuget Package I get from TeamCity contains two extra directories above app_data which is the top level I need to deploy. To get over the Staging deployment problem I have used a different template (Deploy an Azure Web App) than the one that was being used (DeployAzureWebApp). The first one had pre/deploy/post scripts in place in which I think pre was pulling out the app-data directory and ignoring the rest.

I need to replicate this but the template I am now using does not appear to allow scripts. I have read a little about OctoPack and wonder if there is a step I can include that will reformat the package for me or if I should go back to team city and get it to create the package as required.

I am trying to use TeamCity and Octopus Deploy for a CI/CD process of a solution built on .NET Core 2.0. I am having trouble with configuring the build steps in teamcity correctly, as I do not get any packages created. I am using the .NET Core Plugin for TeamCity with the corresponding steps:

• 'dotnet restore'
• 'dotnet build'
• 'dotnet pack'
• 'dotnet publish'

I also include a 'OctopusDeploy Package' step, but as there is no packages produced, so this step does nothing.

The poject does not contain any .json files for the project (only some config files), but .csproj files. I am new to this whole CI/CD process, but I have successfully implemented it for a .NET Framework 4.6.1 solution using octopack.

Any idea on how I can solve this? Any feedback is greatly appreciated.

I need to package an Azure function app that we've built in TeamCity as a Nuget package for deployment via Octopus Deploy. Standard practice would be to use MSBuild and OctoPack but with Azure Functions this will not work as the function.json files are created after the build is complete and they would therefore not be included in any package that OctoPack creates.

So I need to build first and then create a package from the \bin\Release\net471 folder. Would be grateful to hear peoples opinions on the best way to acheive this?

I'm trying to set up a Jenkins build project with ReadyRoll. Mostly it is working but I'm getting warnings that concern me:

I have a Visual Studio 2017 project for building an Azure Function App. This project contains (amongst others) two NuGet packages - Microsoft.NET.Sdk.Functions and OctoPack. The packages are referenced in this order by the .csproj file for the Project in question.

The Microsoft.NET.Sdk.Functions package contains the target _GenerateFunctionsPostBuild -

I have a solution with many projects, about a dozen of which have Octopack installed and packages are being produced correctly when TeamCity runs msbuild /p:RunOctoPack=true /p:OctoPackEnforceAddingFiles=true. As you can probably tell from the p:/OctoPackEnforceAddingFiles flag, each project with Octopack installed also has a nuspec file.

The problem we're having is that Octopack is not honouring the nuspec placeholders as specified at https://docs.microsoft.com/en-gb/nuget/reference/nuspec#replacement-tokens. The one we want to use right now is $id$ which should equal the assembly name of the project being packaged. Instead, when we run Octpack, that $id$ token is empty.

I can see at https://octopus.com/docs/packaging-applications/creating-packages/nuget-packages/using-octopack#UsingOctoPack-Replacementtokens that Octopack allows one to manually override these tokens, but that doesn't help me since Octopack is run on the solution, but I need the name of the project that is being packaged.

What can I do to get around this issue? At the moment we essentially have the project name hardcoded in the nuspec files, but this is becoming brittle and unwieldy and we'd like to fix it.