Adding Components advantages & disadvantages
Hi,
I had one default component created automatically with the creation of a stream and I have loaded my sample project in that default component and I am building my project successfully.
Q. Why do we need to add more than one components? (As I can achieve my work from one component) OR In which cases I need to add more than one components and would be the advantages of it?
Q. Is there any additional steps in build definition, If I have to build more than one components for a particular solution/project? (I am able to build project successfully with one component)
Note: I am using Visual Studio Client
Regards,
Muhammad Moid
I had one default component created automatically with the creation of a stream and I have loaded my sample project in that default component and I am building my project successfully.
Q. Why do we need to add more than one components? (As I can achieve my work from one component) OR In which cases I need to add more than one components and would be the advantages of it?
Q. Is there any additional steps in build definition, If I have to build more than one components for a particular solution/project? (I am able to build project successfully with one component)
Note: I am using Visual Studio Client
Regards,
Muhammad Moid
3 answers
Some reasons to have more than one component.
- If different sets of files need different read access ... the easiest way to arrange this is to have the files with different read access stored in different components.
- If you want to be able to select a different baseline of a particular set of files, while leaving the rest of the files unchanged. Having that set of files be in a separate component makes this easy.
- If you want to make it easy to load one set of files without loading the other files. Putting that set of files into its own component makes this easy.
Build definitions with multiple components are no harder than those with a single component.
- If different sets of files need different read access ... the easiest way to arrange this is to have the files with different read access stored in different components.
- If you want to be able to select a different baseline of a particular set of files, while leaving the rest of the files unchanged. Having that set of files be in a separate component makes this easy.
- If you want to make it easy to load one set of files without loading the other files. Putting that set of files into its own component makes this easy.
Build definitions with multiple components are no harder than those with a single component.