I don't see your attachment, can you e-mail it to info@dvtk.org.

If you update to the latest versions these issues should be solved.

The new released Definition Files do contain a Definition File for the Hanging protocol.

The new versions released (DVT 2.6.6) are ready for use on 64 bit Windows. The issue was indeed because of the 64 bit.

I believe you can define this value for the attribute also as a string without the need to convert it to a float value.

With new you generate a value that is automatically labeled at the same moment. Label is used to label a value that was received.

It is not on the roadmap and I don't expect it do be. I do agree that for certain situations this would be a powerful future.

Against which .NET Framework are you trying to compile this. Because of some internal development we will be working on compiling against the .NET 3.5 framework so might run into these same issues.

Hi Sara,

there are some known memory issues with the DVTk Library. Although all allocated memory should indeed be released when a DICOM Thread is destroyed this is not the case.
In the lower C/C++ layers are still some hard to find memory leaks.
My suggestion would be to do the open en modification of the DICOM files in a separate application process and use a control process to iterate through all the DICOM files. This ensures memory is released.

Good luck, Floris.

Question is if this is due to the fact that you use the new Visual Studio 2010 or that it is some other error.
A common issue we have is that there is a space in the path containing the source code root folder. Can you check that?
Do you still have Visual Studio 2005, maybe you can use that to verify that it is a 2010 specific issue.