Home → Problems →

Octopus in VS 2026 image

• Edit

Steen Tøttrup

19 Aug, 2026 08:41 AM

Hi

I'm switching to the VS2026 image, and run into a few issues with Octopus deploy.

Octo pack is no longer possible, so I've switched to using "octopus package" and that seems to work fine, but once that is done and the package is to be pushed to our Octopus server, I get an error:

Successfully created package Skolevisioner.STILProxy.1.0.0.7-Release.nupkg
Collecting artifacts...
Found artifact 'Skolevisioner.STILProxy.1.0.0.7-Release.nupkg' matching 'Skolevisioner.STILProxy.1.0.0.7-Release.nupkg' path
Uploading artifacts...
[1/1] Skolevisioner.STILProxy.1.0.0.7-Release.nupkg (2,683,313 bytes)...100%
Deploying using Octopus provider
Publishing package(s) to Octopus...
The system cannot find the file specified

What else has changed? What file is it that can't be found?

Thanks,
Steen

1. Support Staff 1 Posted by Feodor Fitsner on 19 Aug, 2026 07:52 PM

   

   Hi Steen,

   VS 2026 image includes a newer version of Octopus CLI which is not yet compatible with AppVeyor Build Agent. Agent expects octo.exe in PATH while new CLI is octopus.exe.

   A few options to fix/workaround:
   1) Use octopus.exe command directly, without deployment provider.
   2) Try copying octopus.exe to octo.exe with:

   copy "C:\Tools\Octopus\octopus.exe" "C:\Tools\Octopus\octo.exe"
   

   3) Download previous Octo CLI during the build, unpack it, and add to PATH.

   Hope that helps.

   • Edit

2. 2 Posted by Steen Tøttrup on 21 Aug, 2026 06:04 AM

   

   Hi

   I got "octopus package" working, but still haven't got it pushing the package to our Octopus server.
   Any idea when you'll get around to looking into this? The end of support for dotnet 9 is in November, and we have 5-6 projects we need to move to dotnet 10, but if we can't deploy them without Octopus.

   Thanks,
   Steen

   • Edit

3. Support Staff 3 Posted by Feodor Fitsner on 21 Aug, 2026 05:34 PM

   

   If you are deploying from a build use octopus command directly with deploy_script section in yaml.

   • Edit

4. Support Staff 4 Posted by Feodor Fitsner on 21 Aug, 2026 05:37 PM

   

   We will be working on the fix, for sure, but please see if you can switch to using octopus command directly.

   • Edit