TFS build best practise
-
Hi, I'd like to know the best practise for this situation : Once upon a time, there was a project (A), whose output is mixture of exe and dll files. One needs to create an installation package using the InstallShield and to have also the installation package in version control. The build should run on the build server. As fas as I know there are two usable ways, how to setup this: 1. one solution S with project A and second InstallShield project. The input for the InstallShield project would be the primary output of the project A. The build solution BS will include this solution S. The dll files are not in source control, however there is a possibility to build them. 2. one solution S1 with the project A, that would have after build process - copy output to some destination. Second solution S2 with setup project that takes input from that destination, as a prebuild action it makes check-in of the dll files. The build solution BS will include this solution S2. The dll files are in the source control (preffered). I don't know whether it is possible to set some prebuild action to InstallShield (LT version). If you have some ideas how to solve things like this please share it. Maybe there is some really simple solution that I don't know. Thanks :)
-
Hi, I'd like to know the best practise for this situation : Once upon a time, there was a project (A), whose output is mixture of exe and dll files. One needs to create an installation package using the InstallShield and to have also the installation package in version control. The build should run on the build server. As fas as I know there are two usable ways, how to setup this: 1. one solution S with project A and second InstallShield project. The input for the InstallShield project would be the primary output of the project A. The build solution BS will include this solution S. The dll files are not in source control, however there is a possibility to build them. 2. one solution S1 with the project A, that would have after build process - copy output to some destination. Second solution S2 with setup project that takes input from that destination, as a prebuild action it makes check-in of the dll files. The build solution BS will include this solution S2. The dll files are in the source control (preffered). I don't know whether it is possible to set some prebuild action to InstallShield (LT version). If you have some ideas how to solve things like this please share it. Maybe there is some really simple solution that I don't know. Thanks :)
tomas.ivan wrote:
there was a project (A), whose output is mixture of exe and dll files.
tomas.ivan wrote:
The dll files are not in source control, however there is a possibility to build them.
Either those two statements are mutually exclusive or you think that the dlls need to be in source control after the build complete. For the second part the dlls need no more been in source control than the install executable is. Ignoring that and looking at a high level view then... A configuration management (CM) person is a person whose job or at least a principle role is to do builds. And only do builds (the role.) And given the following two possibilities. A - Two solutions. One used only be developers. Second that includes projects of first solutions in addition to install shield. B - One solution. Includes common developer projects and InstallShield. With a CM person/role then use A. If not then B. Might keep in mind that InstallShield licenses, specifically cost, might require at least a CM role (versus every developer managing InstallShield.)