02-08-2006 06:36 PM - edited 02-08-2006 06:36 PM
Message Edited by Dynamik on 02-08-2006 06:38 PM
02-09-2006 03:10 PM - edited 02-09-2006 03:10 PM
Yes unique names is the only easy way. In LabVIEW 8 you could also try to fiddle with the contextes to get the DLL code to execute in it's own application context but that is probably a bit of a hassle.
@Dynamik wrote:
Greetings!,I want to use a DLL to encapsulate some LabVIEW code so the DLL and caller can be updated independently. However, there are some utility VIs used by both the caller and the DLL. After the DLL is compiled, if the utility VI changes in the caller, it breaks the DLL. If the utility is changed in the DLL, the caller loads first, and it breaks the DLL.Is use of unique-names the only way to cure this behind-the-scenes dependency? I was hoping for some compiler option, but don't see one.Thanks.Message Edited by Dynamik on 02-08-2006 06:38 PM
Message Edited by rolfk on 02-09-2006 10:10 PM
02-11-2006 09:31 PM
@rolfk wrote:
(Or you could create the DLL in a different version than the LabVIEW version your want to call it from. Then the DLL is most probably even running in its own runtime process 😉
Rolf Kalbermatter
( lol, me thinks you're reading too many threads ;^) )
Thanks Rolf.
Unique-named everything ( would like to see a compiler option to do this...)
02-12-2006 03:15 AM
There are several project renaming tools floating around. You can probably even use OpenG's mangle\unmangle name VIs (in the app control palette) for automating it somewhat.
@Dynamik wrote:
Unique-named everything ( would like to see a compiler option to do this...)
05-28-2010 05:08 AM
I have now the same problem and I posted here:
http://forums.ni.com/ni/board/message?board.id=170&message.id=501169&jump=true#M501169