Offline drop variable replacement issue

I’m seeing a strange issue with offline package drops not replacing path variables properly. I’m using 3.4 beta 2. The standard tentacle deploy works great, but for one of our customers we have to use offline packages. This is the first time we’ve done it, so I can’t say if it worked on 3.3 or not.

All the config transforms work fine, but anything relating to paths aren’t. I’m using the “IIS Application - Create” script ( and for the “Physical Path” i have the following set “#{Octopus.Action[My.Web.Package].Output.Package.InstallationDirectoryPath}” (I’ve substituted the name of the actual package)

With the tentacle deploy, it gets replaced correctly. Through the offline drop, it actually sets the path to be that raw string.

I’m going to create an offline drop for my dev environment here and see if I encounter the same issue.

Has anyone encountered this before?

Looks like it’s this issue. I did not realize this wasn’t supported. This should probably be in the documentation so people don’t get blindsided by this.

Hi Mark,

Thank you so much for the feedback and giving the UserVoice more attention. I have updated the documentation to include this at:

Kind regards,