I have absolutely the same problem
I checked All Applications > AppName > Application versions and it's ok, i see list of deployments from VS and AppVeyor. Moreover, nothing is changed when i switch among thouse versions. The version is worked fine that was published via VS, not AppVeyor
@korenb Yeah I never found the root cause. We're still doing manual deploys since neither AppVeyor nor Amazon have taken ownership of the issue.
The next step I was going to try was to deploy using the AWS CLI using the same commands defined in the AppVeyor deployments. If that works from the CLI, it points to an AppVeyor issue. If it does not, it points to an Amazon issue. I suspect it will not work from the CLI.
@korenb Thank you for update! We have a hard time reproducing it. If you could share some response from Amazon support here, it would be great.
Also if you (or @nick.young.356) by any chance can try to create new beanstalk application (side by side with existing one), and run the same script (with only -DEnvironment.Name changed) against it, will it help?
Original problem described in this issue was related to the fact that DeployIisAppPath should be set to Default Web Site in publishing profile when packaging, as described in step 10 here. New Beanstalk specific packaging option takes care of that.