Reload external files ?

[Philipp_Elhaus]

I have a problem that's sort of a big pain in the a** :

I'm developing in VisualStudio .NET DLL's that then get used in LabView. 

Whenever i re-compile the DLL in VisualStudio (cause i did some minor changes) i have to:

1. close LabView entirely down
2. re-open LabView
3. reload the VI where the DLL is used
4. delete the .NET Constructor-Node that references that DLL
5. re-add the .NET Constructor-Node to reference the new DLL
6. also delete & re-add all invoked methods & properties i connected.
7. re-connect that .NET Node to the other elements

I have to do this because LV is caching like hell and there's literally no way to tell if it did load the new version until i do this burdensome procedure everytime. I've burned so much time already on this over the last week and this is slowing me down massivly.

Is there some sort of "RELOAD/REFRESH all external dependencies" button (sort of a Webbrowser "F5 key" just for LV) ?

[Bob_Schor]

The answer is almost surely "No".  If you think that this is something that many LabVIEW Developers would like, submit it as a proposal on the Forum "Idea Exchange", which is designed to let LabVIEW Users tell NI what new features they need.

Bob Schor

[ESiTo]

Hi

The same issue and so far, no clean solution. 

Imagine that for every single modification or debugging, you must do it again. 😞

Thanks for your consideration

[paul_cardinale]

There is this,

But I doubt that it would cause a reload.

[santo_13]

---

@ESiTo wrote:

Hi

The same issue and so far, no clean solution. 

Imagine that for every single modification or debugging, you must do it again. 😞

Thanks for your consideration

---

Better to use a .NET code to debug the DLL instead of using LV to debug the DLL.

[Kyle97330]

I know it's too late for the original post 3+ years ago... but I have found that if you create a new DLL with the same version number then you have all of these problems, but if you have a new version number you only have a subset of these problems:

You do still need to do this (swapping the old DLL for the new one in between numbers 1 and 2):

1. close LabView entirely down
2. re-open LabView
3. reload the VI where the DLL is used

But you do NOT need to do this UNLESS you are using .NET generics (such as Lists<>):

4. delete the .NET Constructor-Node that references that DLL

5. re-add the .NET Constructor-Node to reference the new DLL

6. also delete & re-add all invoked methods & properties i connected.

7. re-connect that .NET Node to the other elements

Even if you are using .NET generics then the only thing you need to do is number 6 and 7 on a few specific nodes that use said generic.

I'm not saying it's not a pain (it is) but it's not as severe by far if you just increment your version each time you build a new one.