Azure Cloud Service package format

Legacy Uncategorised
1

Hi,

I am currently working on deployment of Azure Cloud Service project, and we have some problem with deployment using Octopus Deploy.
Actually it works when it deployed from Visual Studio but it’s doesn’t works when it deployed using Octopus Deploy.
I started investigate that and noticed that package produced by Octopus differs from the one generated by Visual Studio.
VS package:

_rels
76d89716-c5a0-4c39-903c-1a36b5bef07d.csman
mResearchSurveyEngine_40a6cfe9-b480-431d-8c84-536dde598e4c.cssx
NamedStreamPackage_79fe36b6-9a4b-41c5-a721-2c9f0c16e708.csnsx
SDPackage_cec97acf-e864-44a4-af3b-c2b5f954b70e.csdx
SMPackage_9cbb53f7-0307-430f-b557-86f79fc5e4bd.csmx
[Content_Types].xml

And After Octopus Deploy it looks like this:

LocalContent
NamedStreams
ServiceDefinition
_rels
package.xml
[Content_Types].xml

I am not sure that actually package format cause problem but how can I use the same package format as Visual Studio, or how to avoid any changes to package and just deploy it without modifications?

Thanks
Ihor

2

Hi Ihor,

Thanks for getting in touch!

To ensure Octopus doesn’t pack/unpack your package, add this variable to your project and set it to True … Octopus.Action.Azure.CloudServicePackageExtractionDisabled.

Hope that helps!
Mark

3

Thanks Mark, that is exactly what I wanted. One more question where can I find other variables like this?

4

Hi Ihor,

You can find the full list of variables in our documentation here.

Hope that helps :slight_smile:
Mark