11

Everything works as expected but I would like to improve the directory structure that the .zip produces.

When I create a deployment package I have it create in a custom directory which works fine but the .zip it creates is in the structure of:

content/c_c/users/pcName/documents/VS2010/Projects/ProjectName/obj/release/package/packageTmp

Only in the packageTmp directory do I get to the files I want!

Is there a way for the created zip to not include all of those empty directories?

C. Ross
  • 31,137
  • 42
  • 147
  • 238
KevinUK
  • 5,053
  • 5
  • 33
  • 49

1 Answers1

1

I never understood the folder structure either. By using msdeploy to publish the site it uses that folder structure to deploy multiple sites/assets at once. It's annoying when looking at the package itself but it does "work". Just use msdeploy to actually deploy the package and you don't have to look at the crazy folder structure. :)

Paul Lemke
  • 5,494
  • 3
  • 47
  • 66
  • +1 it's completely crazy. Always get asked about it when people go poking in the zip files. – Deleted Oct 11 '11 at 22:08
  • I am not quite sure if "Just use msdeploy and you don't have to see the mess" is an appropriate stance in development. I can't use msdeploy, for example, and still would enjoy if the files were 15 levels higher in the ZIP. So I suppose it all is just "impossible". – Cornelius Jun 10 '13 at 17:38