So I was happy to confirm that Visual Studio solution files (sets of projects, each representing one library or executable or whatever) can in fact be built from the command-line, an essential interface for most automated build / test environments. However, I was nonetheless greatly frustrated to find that the cmd-line MSBuild simply skips over .vdproj projects, the logical "final" project in many common solution patterns which then takes all the previously compiled libraries, applications, documentation and what-not and packages it into a tight little .msi installer file.
Being able to automate generation of your code is grand, but that final skipped step kind of undermines the whole point of automated release management, including "testing what the customer will install." Bizarre.
No comments:
Post a Comment