.NET Core Deployment

Simon Martin-Lemmon's Avatar

Simon Martin-Lemmon

07 Oct, 2016 12:49 PM

Hi,

I am sure this has been asked a million times already, but cannot find anything similar.

We are trying to build and deploy an ASP.NET core applications, using TFS (Visual Studio Online) and Octopus.

I have reviewed the documentation at

http://docs.octopusdeploy.com/display/OD/Deploying+ASP.NET+Core+Web+Applications

I am still struggling.

For all our other applications, we were using Octopack followed by a "Create Octopus Release" TFS Task.

Octopack no longer seems to work.

I am trying to use an "Octopus Package Application" TFS task, but am unsure of what to put in most of the parameters.

On other thning that we did in OctoPack was to append "develop", "release" or "hotfix" to the end of the package name to determine which channel etc to use.

I cannot see how to do this either.

This is what we were using in the TFS msbuild arguments...

/p:RunOctoPack=true /p:OctoPackPublishPackageToHttp=http://xxxxxx:1234/nuget/packages /p:OctoPackPublishApiKey=API-123456xxxxx /p:OctoPackAppendToVersion=develop

Any help and guidance would be very much appreciated.

Many thanks in advance

Simon

  1. Support Staff 1 Posted by Daniel Fischer on 11 Oct, 2016 06:30 AM

    Daniel Fischer's Avatar

    Hi Simon,

    Thanks for getting in touch! There is something that stands out here.

    For all our other applications, we were using Octopack followed by a "Create Octopus Release" TFS Task.

    The TFS step does not use OctoPack but Octo.exe pack instead. As OctoPack is not compatible with ASP.NET Core.
    We have updated the documentation page that you linked to give you more accurate information.
    http://docs.octopusdeploy.com/display/OD/Deploying+ASP.NET+Core+Web...

    As for what parameters you need to enter, you should only need to fill a couple of mandatory fields in TFS:

    Package ID - Name for your package.
    Package Format - NuPkg or Zip
    Package Version - Versioning for your package.
    Source Path - Path for your packaged build source files.
    Output Path - Destination path for package.
    

    We have an example at the following URL: http://docs.octopus.com/download/attachments/3048587/PackageApplica...

    Let me know if that helps.

    Regards,
    Daniel

  2. Paul Stovell closed this discussion on 11 Jan, 2017 07:03 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac