We recently started using Gulp for our front end build process and that’s been enormously helpful in consolidating how and where our front end technologies were generating output. This led to us having a bunch of extra files that were now generated at build time and didn’t actually exist in the csproj. Unfortunately, we were at a loss as to deploy these, and what’s worse, we had 3 different ways that we deploy our web applications. We needed a solution that works with
- Web applications deployed to IIS via webdeploy
- Web applications deployed to Azure Web Sites via webdeploy
- Web applications deployed to Azure Web Roles via package
It’s a shame that there isn’t a consistent way of listing all the files to deploy, but, we are able to get all the files deployed that we need deployed. Ultimately, there were 2 customizations needed to be made for the final solution.