bug

Just spent a little while looking into this. I thought I’d be clever and add my build script to the solution it builds so I can get some intellisense from Resharper (although it’s somewhat limited). This added the file into ‘Solution Items’ which is a virtual folder.

I found a cracker of a bug (undocumented feature) this morning that was keeping me ‘amused’ for a couple of hours. I was trying to use Visual Studio 2003 Installer to create a Setup package to actually deploy setup packages (yes, you read correctly!) to a number of ‘deployment’ servers. These are localised servers where users pick up new versions of software (we’re not quite at one-click deployment yet 🙂 ).

I was using a checkbox dialog to give options on which servers to deploy to, and was then using the properties set in the dialog to control whether the specific ‘custom folders’ (public shares on the different servers) were deployed. This doesn’t work!

You actually have to ensure that you don’t specify a condition at the folder level, and then select all files and add the condition there (for all files).