I have a solution with a small number of projects, 3 of which are based on web interfaces (WCF on the IIS / MVC website). When the solution is built, it unloads each of the components of this distributed system into the "Build" folder. Running part of the "configurator" of all output will automatically install the system in the cloud. This is very neat :) However, web deployment projects are a big pain. They “build” (that is, deploy) each, one, time that I create, even if no changes have been made to their respective projects.
One line of code changed? Look ahead to wait about a minute for 3 web projects to be redistributed.
[These projects are currently very simple: two have one .svc file and one .ashx, the other is an MVC application with ~ 5 views)
I understand that I can change the configuration of solutions so as not to “build” them, but I did it, and it’s very easy to log in the next day and forget about it, and also spend a couple of hours tracking errors in distributed systems because of which simply not built.
Why am I using web deployment projects? Well, because I need all the pages + binaries from the web project. The build output for the project itself is the bin folder, so there are no pages. The entire project folder? It has .cs, .csproj and other files that I do not want to include.
, . - . ?