tfs - Deploy Custom Build Activity to clients -


when creating custom build activities tfs 2010/2012 results in assembly (dll) files can used in build definitions.

when developing locally place assembly in gac or visual studio probing folder. build controller place assembly in source control (tfs) , tell controller look.

all fine , working nicely.

the thing other developers (quite lot) on other machines need assembly when starting new builds. how deploy new versions of assembly?

assemblies retrieved tfs source control location defined controller tmp folder visual studio , loaded scope when opening build definition edit (and when open queue dialog).

you need assemblies in gac (or vs private assemblies folder) if editing template itself, adding xaml template activity project allows bypass gac mess namespace imports in xaml resulting in errors in tfs.

another caveat if activity assembly using library assembly 2nd dll may not picked correctly - workaround add fake empty activity library.


Comments

Popular posts from this blog

c# - DetailsView in ASP.Net - How to add another column on the side/add a control in each row? -

javascript - firefox memory leak -

Trying to import CSV file to a SQL Server database using asp.net and c# - can't find what I'm missing -