Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
3521
TFS Build Server indirectly referenced assemblies...
posted

I am building a Web Application on a TFS build server which does not have Infragistics installed on it.  This is achieved by checking in local copies of the resources required by Infragistics.  This approach is taken because this build server serves dual duty as an application server in my dev environment for the purposes of testing deployments.  We are currently not installing IG on our deployment servers.  Depending on the type of build being performed, it may deploy to dev, qa, or production servers upon successful compilation.

The build works successfully with a caveat as it relates to indirectly-refereced assemblies.  My application does not reference these assemblies at all, however during the code analysis (FxCop) stage of the build, some warnings are thrown about these indirectly referenced assemblies.

So, the series of questions might go something like this:

1) Would a better approach be to have a dedicated build server with the IG products installed?  Keep in mind the intention of not installing the products is to keep the solution isolated in terms of patches from IG in the future.

2) Do we know which referenced assemblies could trigger these indirects?

3) Should I just change the application to include these indirects?

 

 

Parents
No Data
Reply
  • 3521
    posted

    Duh.  If you read the warning close enough, it lets you know which is trigger the indirects.  Sorry.

Children
No Data