I'm wondering what others use as a tool for creating the final package to hand over to the customer. For now, these are the tasks it should perform for our company:
- build a set of VS projects (C#,C++); which set depends on configuration on commandline of preferrably in a file
- copy some of the outputs (dll,exe) and header files; should again be configurable: not all customers get the same functionality)
- make a zip file for each configuration
Additional features that are not yet needed now, but might be in the future:
- upload it to a website of some kind (we're still not sure what we're going to use.. might be ftp or vesrionsing system). Well, actually, it would be awesome if the tool could create an entry on a Confluence page.
- instead of zip files we might switch to installers, though that shouldn't change too much I guess
Right now I have the first steps covered in a batch file that takes some arguments, and a master batch file that calls it for each configuration. It works, but I can't get used to the batch syntax and I'm now building by invoking devenv.exe which seems slow and is error-prone as it takes the .suo file into account.
I was thinking about doing everything again in msbuild, but first I'd like to hear more opinions on this. I'd also want to know what kind of tools big companies use for large products.