How to build DVT |
This page describes the steps that must be performed to build a version of DVT.
Pre Requisites
• Have Microsoft Visual Studio 2005 available with all the latest updates and patches.
• Access to the CVS repository of the DVTk Project on Sourceforge.net.
Repository Checkout
Do a new clean checkout of the Core and Definition module from the Best Repository to the same location. Make sure that it is stored in a folder path that before the dvt core and definition folder doesn’t contain any folders with spaces in the names. You should now have something like:
D:\Dvt\Best\definitions\
D:\Dvt\Best\dvt core\
Build Definition Merge Module
Open the DICOM Definition Files solution from definitions\Merge Module\DICOM Definition Files.sln. When the solution is loaded in Visual Studio 2005, switch the configuration to Release. See also figure below.
Afther switching configuration build the merge module and verify that the build is successful and contains no errors. Close the Visual Studio application.
Define Version
To set the version for the dll and exe files of the project, run the set version command.
The syntax is: SetVersion.exe source x.x.x.x
You should replace x.x.x.x with the appropriate version number like in figure below.
More information on the usage of version numbers can be found in the version numbering convention document.
Build DVT
Open the DVT solution from the location dvt core\source\solution\Dvt\dvt.sln. When the solution is loaded in Visual Studio 2005, switch the configuration to Release. See also figure below.
After this a build action for the DVT project should be started. This can be done by right clicking the DVT Project and selecting Build. See also the figure below.
When building is complete, verify that no errors are reported.
Build Setup
In the Solution Explorer, go to the DvtSetup project. Click it once to view the properties in the Properties Window. Update the “Product Name Property” to reflect the new version number. Only the first 3 digits of the version number are filled in here. Update also the “Version” property to the new version number. Use here also only the first three digits of the version number. After updating this last property Visual Studio will show the message from the figure below. Click Yes to update the ProductCode.
Exclude the following double Detected Dependencies by right clicking them and selecting “Exclude”. See also Figure 5 for more information. This action needs to be done for the following dependencies:
• AxInterop.SHDocVw
• Interop.SHDocVw
When this action is performed the setup can be build. Verify that the setup is build successfully and no errors occur.
Testing
Test the installer in a clean virtual machine. Verify that the example projects load and the scripts from the example projects can be executed. Run the SQA scripts before releasing.
Tag Source Code
A last step in the process is to tag the source code. In this example we use TortoiseCVS for the tagging. Right click in Windows Explorer on the dvt core folder and nativage to Tag in the TortoiseCVS context menu. In the screen fill in the version number of the release seperated by underscores (2_3_1_0). And then click on ok. See also the figure below.