You are on page 1of 4

Release Notes - DVTK

Copyright Statement
Copyright © 2001-2005
Philips Medical Systems NL B.V., Agfa-Gevaert N.V.
All rights reserved.

Legal Notices Information


Third Party Components Used By DVTK
- Bison
- OpenSSL
The next section outlines the Third Party components used in DVTK, which are
covered by additional license terms.

Third Party component license terms


See; http://www.gnu.org/software/bison/
See; http://www.openssl.org/

Scope
This document contains release notes for DVTK (DICOM Validation ToolKit).

What's New in this Release


The items listed in this section provide an overview of the most important new
features in this release.
1) Tests can now also be developed using;
- MS-Script style scripts like VBScript and JScript.
- .NET calls to DVTK from any .NET ready test-framework such as NUnit.
- DICOM Script (DS/DSS) language is still supported.
2) Test results are outputted as structured XML.

Components
DVT.exe – .NET user interface application to perform DICOM testing.
DVTCmd.exe – .NET command-line application to perform DICOM
testing.
DvtkScriptSupport.dll – .NET script engine that runs MS-script based DICOM test
scripts.
DVTK.dll – .NET class library providing DICOM test capabilities
DvtkData.dll – .NET class library providing basic data-classes for DVTK
DVTKManagedCodeAdapter.dll –
.NET Managed Extension for C++ library that wraps core DVTK C/C++ routines.

Hardware/Software Information
The following table provides minimum and recommended system configuration
requirements for DVTK.
Software Requirements
The following operating systems are supported:
Windows NT 4 SP6a
Windows 2000 Professional
Windows 2003 Server
Windows XP Professional

Supported Platforms
Microsoft .NET framework 1.1
Microsoft Visual Studio .NET 2003

Getting Started
Starting DVT
Either;
- Use DVT or DVTCmd as end-user applications.
- Integrate your own test framework/applications with the DVTK API.
- Host the DvtkScriptSupport in your test framework/applications.

Accessing Help
Available help
- User manual
- Tooltip
- DVTK Class Library Documentation
- DvtkData Class Library Documentation

Restrictions and Guidelines on Using this Release


See the supplied license.txt file.

Known Issues in this Release


Important
FIX: The bool Type Does Not Marshal Correctly from Unmanaged Code
Compiling the code with this fix requires a patched visual studio!
RESOLUTION
A supported fix is now available from Microsoft.
See Microsoft Knowledge Base Article - 814472

Category ID Description
Build code 1 Visual Studio 2003 contains a bug when switching between build
configurations <Debug|Release>.
The build dependency between DvtkManagedCodeAdapter and
DvtkData is not correctly updated.
This may result in incorrect builds.
Work around:
This work around ensures that VS finds the correct dependencies
during restart of VS.
Either;
1)
Ensure deletion of all binaries of the old configuration.
Binaries in bin, release and debug directories of DvtkData,
DvtkManagedCodeAdapter and DVTK.
or;
2)
Build solution in new configuration. Then close VS. Restart
VS. And build again.
MEC++ 2 http://support.microsoft.com/?id=814472
Runtime Microsoft Knowledge Base Article - 814472
PRB: Linker Warnings When You Build Managed Extensions for
C++ DLL Projects
To fix this bug DVTK contains DVTK.Setup.Initialize() and
DVTK.Setup.Terminate().
See;
ms-
help://MS.VSCC.2003/MS.MSDNQTR.2003JUL.1033/vcmex/html/
vcconConvertingManagedExtensionsFor
CProjectsFromPureIntermediateLanguageToMixedMode.htm
MEC++ 3 http://support.microsoft.com/default.aspx?kbid=823071
Runtime Microsoft Knowledge Base Article - 823071
FIX: The bool Type Does Not Marshal Correctly from Unmanaged
Code
A VS patch is required to fix this bug.
Needed to correctly build the DVTKManagedCodeAdapter!
CRT Runtime 4 The proper CRT (C-runtime) needs to be used with the DVTK
component.
http://support.microsoft.com/default.aspx?scid=kb;en-
us;140584
Microsoft Knowledge Base Article - 140584
HOWTO: Link with the Correct C Run-Time (CRT) Library
See;
ms-
help://MS.VSCC.2003/MS.MSDNQTR.2003JUL.1033/vclib/html/
_crt_c_run.2d.time_libraries.htm
DVTK depends on redistributable dlls;
MFC71.dll
MSVCP71.dll
MSVCR71.dll
MFC Runtime 5 The proper MFC runtime needs to be used with the DVTK
component.
http://support.microsoft.com/default.aspx?scid=kb;en-
us;140584
Microsoft Knowledge Base Article - 140584
See;
ms-
help://MS.VSCC.2003/MS.MSDNQTR.2003JUL.1033/vccore/html/
vcoriRedistributingMFCATLOLEDBTemplatesApplications.htm
DVT depends on redistributable dlls;
AxInterop.SHDocVw.dll
Interop.SHDocVw.dll
MEC++ 6 BUG: AppDomainUnloadedException is thrown when you call a
Runtime virtual destructor on a __nogc class during an AppDomain
unload
See http://support.microsoft.com/default.aspx?scid=kb;EN-
US;837317
Workaround introduced in DVTK.dll
MEC++ 7 BUG: Linking Mixed-Mode MEC++
Runtime Converting Managed Extensions for C++ Projects from Pure
Intermediate Language to Mixed Mode.
See
http://msdn.microsoft.com/library/default.asp?url=/library/en-
us/vcmex/html/
Vcconconvertingmanagedextensionsforcprojectsfrom
pureintermediatelanguagetomixedmode.asp
This is done because linking with an entry point causes managed
code to run during DllMain, which is not safe (see DllMain for the
limited set of things you can do during its scope).
Workaround introduced in DVTK.dll.

You might also like