01-15-2007 11:32 AM
01-18-2007 04:49 PM
Hi,
Try to add the VI to a LabVIEW project and open the VI from the project explorer. After running the VI, you can then close both the VI and LabVIEW project before rebuilding the COM object.
Attached is a LabVIEW project file I created with this VI.
Tunde.
01-18-2007 05:26 PM
01-19-2007 02:04 AM
Well, not sure about projects but in pre project times this has been a very common issue with LabVIEW. Using DLLs with the Call Library Node I regularly ran into the situation that I had to shutdown LabVIEW in order to recompile the DLL and use that new one. Closing down the VIs just wasn't enough. It's some time I did serious DLL debugging so I will have to try this with projects sometimes.
@Tunde A wrote:
Hi,
Try to add the VI to a LabVIEW project and open the VI from the project explorer. After running the VI, you can then close both the VI and LabVIEW project before rebuilding the COM object.
Attached is a LabVIEW project file I created with this VI.
Tunde.
01-19-2007 10:46 AM
The main issue for LV is that we do not spawn off another process when running the VI - it is done all in the same process as the IDE. This is very different from other IDE's, such as Visual Studio. This also has impacts on what can be released.
Currently, you are correct - once you load up certain components, they are locked in memory and you must recycle LV to release them. We are always working on ways to remove this restriction, but it is often very compex or out of our hands all together.