TFS BuildDefinition - Environment based dlls
-
Hi, How can I configure my TFS build to pick up dlls based on the build environment. For instance my directory structure is like this:
Source |______ build |______ environment |______ LIB |_____________ DEV |_____________ LOCAL |_____________ PROD |_____________ UAT |______ src |_____________ net |___________________ myProjectDirectory |______ mySolutionFile.slnWhat we are needing to do is to create a build for DEV, UAT and PROD environment. We have some 3rd party dlls which reside in lib > DEV, lib > UAT, and lib > PROD. So essentially for DEV build we need to pick the dll from the lib > DEV directory, UAT build we need the dll from lib > UAT directory .. so on .. you get the idea. Can this be accomplished? I know I havent been able to find a way to do it using Build Definition Wizard. I would appreciate your help. -
Hi, How can I configure my TFS build to pick up dlls based on the build environment. For instance my directory structure is like this:
Source |______ build |______ environment |______ LIB |_____________ DEV |_____________ LOCAL |_____________ PROD |_____________ UAT |______ src |_____________ net |___________________ myProjectDirectory |______ mySolutionFile.slnWhat we are needing to do is to create a build for DEV, UAT and PROD environment. We have some 3rd party dlls which reside in lib > DEV, lib > UAT, and lib > PROD. So essentially for DEV build we need to pick the dll from the lib > DEV directory, UAT build we need the dll from lib > UAT directory .. so on .. you get the idea. Can this be accomplished? I know I havent been able to find a way to do it using Build Definition Wizard. I would appreciate your help.What we have done is to add 3rd party dlls to source control, in your case put the entire LIB folder into source control. Having doe this use relative paths in the references so that when the build server gets the latest code it also gets the matching dlls in the same relative paths.
If you have knowledge, let others light their candles at it. Margaret Fuller (1810 - 1850) www.JacksonSoft.co.uk
-
What we have done is to add 3rd party dlls to source control, in your case put the entire LIB folder into source control. Having doe this use relative paths in the references so that when the build server gets the latest code it also gets the matching dlls in the same relative paths.
If you have knowledge, let others light their candles at it. Margaret Fuller (1810 - 1850) www.JacksonSoft.co.uk
Thanks for answering. Above mentioned is actually the source control folder structure. Perhaps I do not understand the relative path technique, meaning I am not sure if you are referring to relative paths in the Build definitions file of if you are talking about ASP.NET references. Would you mind elaborating it a bit? Thanks again for your help.
-
Thanks for answering. Above mentioned is actually the source control folder structure. Perhaps I do not understand the relative path technique, meaning I am not sure if you are referring to relative paths in the Build definitions file of if you are talking about ASP.NET references. Would you mind elaborating it a bit? Thanks again for your help.
Our Team build builds windows forms, web services and web applications that make up our product in one swoop. The team build just says get the entire folder structure from source control then build the specified solutions. Each solution/project then uses relative paths to any referenced dlls. By default all paths are relative if they are on the same drive. The team build does not need to specify the references as the project does that.
If you have knowledge, let others light their candles at it. Margaret Fuller (1810 - 1850) www.JacksonSoft.co.uk