Click here to Skip to main content
13,094,983 members (83,413 online)

Application Lifecycle

QuestionTFS build best practise Pin
tomas.ivan2-Sep-12 21:19
membertomas.ivan2-Sep-12 21:19 
AnswerRe: TFS build best practise Pin
jschell4-Sep-12 12:15
memberjschell4-Sep-12 12:15 
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

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.)

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

Advertise | Privacy |
Web03 | 2.8.170813.1 | Last Updated 23 May 2017
Copyright © CodeProject, 1999-2017
All Rights Reserved. Terms of Service
Layout: fixed | fluid