LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

identify debug dll

Hello,

 

As part of the development process, I usually create debug DLLs for testing and then finally create a Release DLL. I've named both DLLs as being the same to reduce overhead when managing them. From the finished DLL, how can I identify if it was a debug build or a release build?  This will also help me with my release audit to make sure I didn't screw anything up.

 

I was hoping for something in the Version Info Dialog Box, but this information is common between the two.  I was looking into manifest files, but couldn't find anything obvious.

 

And I'd like to make the process as simple as possible, the best would be to somehow embed it in the version tab in Windows!

 

Thanks,

Jason. 

Message 1 of 3
(3,367 Views)

There is the BeingDebuggedByCVI function, but I'm not sure that's what you are looking for.

It gives you the information but only if the code is being run, of course. 

S. Eren BALCI
IMESTEK
0 Kudos
Message 2 of 3
(3,342 Views)

Unfortunately I'm not looking for a runtime solution, just to update the VERSION_INFO resource depending if it's debug or not.

 

As a workaround, I've currently decided to sign release builds and leave debug builds unsigned. At least from the properties I can view if it's a release or debug build. However, this is dependent on my build configuration and if somebody else builds a release/debug from the same source they need their own certificate.

0 Kudos
Message 3 of 3
(3,322 Views)