Search code examples
.netbuild-automationdevexpressproject-organization

Build Server - install external control libraries (DevExpress) on build server

what's the right way?

We have one build server for our projects. We have different projects, wich reference different versions of DevExpress.

  1. Should we install every DevExpress Version on the build server or

  2. should every project have its own folder with DevExpress assemblies.

  3. Exists an other possible way?

In my opinion:

Advantage 1: It is easier for every developer to maintain his local copy of the project. Disadvantage 1: DevExpress version hell on build sever because every new release must be installed.

Advantage 2: Every project could be builded without prerequisite. Disadvantage 2: Every developer must manually put his dlls in a separate Libs folder. If you have dragged a DevExpress control from the toolbox, you must reorganize your references for this dlls.

Solution

  • I would suggest that you install our installations on the Build server. There will not be a DLL hell on your machine if you install only installation. This will guarantee, that your project will be built using a licensed version of our controls and thus no nag screens in a ready built application. This is what we usually suggest when our customers ask such questions in the support center...