Making my automated build work with visual Studio 2012 and TFS 2010

could solid understanding of automated build process in visual studio/tfs answer few questions me or give me advice?  application , servers taken on different department (along me, thank goodness that) , solution has been put tfs server.  took visual studio 2010 project visual studio 2012 consistent new team, , put code tfs 2010 server in new collection.  of went fine i’m worried getting build process running in new environment.  not have kind of build process in place.  i’m little confused , unsure how build process working.  no unit testing @ issue @ point.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
here’s pre-merger setup far build process concerned; ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

in visual studio 2010 have file called tfsbuild.proj in team build types folder contained lot of xml in defined build (the build machine, team project, build directory path, solution build, files copy, etc…).  created while ago.  believe using visual studio 2003 then. on development server, call ‘appdev’, run tfs 2010 , think recall having install visual studio there make build work. on ‘appdev’ there tfs administration console running , within menu option call ‘build configuration’.  selecting reveals ’controller’ , agent, both of seemed contain default settings (the name of computer running on, ‘appdev’).  don’t think directly use ‘build server’, think needs running work.  correct? run build, execute script on machine whenever need (and every night using scheduled task). within script following command; "c:\program files (x86)\microsoft visual studio 10.0\common7\ide\tfsbuild" start "http://appdev:8080/tfs/defaultcollection" mileg milegnightlyreleasebuild setup has run clock years.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
post-merger setup
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
i’m using visual studio 2012 on computer, , code still being managed within tfs 2010 server it’s on server call devtfs along lot of other code.  solution code in new ‘collection’ called milegcollection.  tfsbuild.proj of course still in solution. still have own development server called devmileg, code no longer resides there, on above mentioned devtfs server. ============================ believe need install visual studio 2012, , portion of tfs 2010 on devmileg server, , somehow same build controller , agent running on devmileg server, yet point tfs 2010 server running on devtfs code. i’m worried , confused few things…  can tfs 2010 compile build visual studio 2012 code?  seems it’s going problem.  there gotya’s pointing @ different computer code build?  please feel free ask me questions if i’ve not made clear or need more info.

thanks!  

hi jjquinn,

thanks post.

as know tfs 2010 invoke msbuild v4.0 command line build project on build agent machine. if want build vs 2012 project using team build 2010, suggest install vs 2012 on build agent machine, manually execute msbuild v4.0 command line build project on build agent machine, if vs 2012 project can built successfully, team build 2010 can build too.

to build vs 2012 solution using team build 2010, should ensure following steps:

1        the solution can built on build agent machine using vs 2012.

2        ensure tfs build service account have permission build solution on build agent machine.

3        ensure solution can built on build machine using msbuild v4.0 command line manually. 

additionally, build solution using team build, need ensure team build service can find required dlls on build machine. using following 2 way reference dlls when using team build:

1        create assemblies folder under solution, , add dlls in folder. after check in solution tfs, team build service solution tfs build on build machine, in case, assemblies folder under solution together. structure this:

                 teamproject

                        /solution1

                                /assemblies

                               /poject1

                               /poject2

                               /…

                        /solution2

                        …

2        create same common folder on build machine created on client, , folder path same. when team build build solution on build machine, try find dlls on build machine follow path set in project.

---

john qiao [msft]
msdn community support | feedback us
develop , promote apps in windows store
please remember mark replies answers if , unmark them if provide no help.

Archived Forums V  >  Team Foundation Server - Build and release management