Home/ Questions/Q 8988835
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-15T22:06:16+00:00

I’m trying to deploy my MVC4 app to ELB. The project has several post-build

  • 0

I’m trying to deploy my MVC4 app to ELB. The project has several post-build steps which pull together dependencies. The AWS SDK publish wizard then does not do the trick – it builds a Web Deploy package behind the scenes, which does not action those post-build steps or preserve the resulting directory structure.

So, I downloaded the command-line EB tools, got a git repository working, but can’t work out the next step: what do I push to the server with git aws.push: because if it’s just the resulting files then I can’t specify the “Enable 32-bit applications” flag (required), etc. Do I then push a web deploy package from my repository?

I presume so, but if so, how do I include the files copied into the output folder during “normal” builds by my post-build steps?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Here we go. This seems to be in conflict with what Jim Flanagan was saying – below it’s a zip file, but Jim says it’s the contents of it.

    @Jim Flanagan – perhaps you could comment if you have some time. Thanks.

    Hi thanks for contacting AWS Premium Support

    Communication from the Elastic Beanstalk Engineering Team.

    When you aws.push an ASP.NET/MVC app you do not push the web deploy archive, rather you push the artifacts as you want them deployed on the machine. From the customers stack overflow question it seems they have already found the local git repo that the VS deployment wizard created and looking their should give them a good indication of what is needed in the git repository.

    There isn’t a nice way through the aws.push to specify what the “Enable 32-bit Application” app pool setting should be (or any other configuration setting). If you need a specific configuration setting set I would suggest creating the environment (via the console or using the eb command line tool) which allow you to specify the configuration. And then use git aws.push to deploy to that environment, git aws.push will just use the configuration that is already present on the environment.

    The last question about still being incremental is not really valid since you are not pushing just one big zip file. But if you were, it could still be incremental depending on what changed in the zip file, it might just send a diff between the two versions of the zip file. As the question implies though that use case is not really what incremental deployments were designed to help with.

    • 0