locked class in multiple apps

[lmd2]

I have a file class that does some initialization, keeps track of paths for storing data, logs, and some config parameters. I am running a RT application and a Windows UI which will only occasionally be connected to the RT which runs in a remote location. The class library is currently shown under the UI target in the project explorer - I would like to have different instances of the class on both targets, Win & RT, both targets need file init, path management. But once I have a reference on the top level of my UI_Main, and my RT_Main the class gets locked and I cannot edit the class; cannot add accessors or methods. What's the right way to do this?

Thanx

lmd2

[nathand]

Sorry, you (and everyone else) are currently out of luck on this. See http://digital.ni.com/public.nsf/allkb/219A8BB7FD8EF0D9862571840053A5E9 and vote for this idea http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Classes-should-not-be-locked-when-added-to-multiple-ta...

[Thoric]

Is it possible that moving your RealTime work into a separate project will keep your class from locking? By keeping your Win target work in one project and the RT work in another you may find that LabVIEW doesn't lock the class.

Also mentioned here: http://forums.ni.com/t5/LabVIEW/Multiple-Application-Instances-Class-Library-Locked/td-p/1971591

[lmd2]

Thanks nathand & Thoric - 

I understand what I need to deal with now. AQ suggested making a second, dummy project on the idea exchange. Add the class (or classes) to this project. Then when edits needed to be made to the class, close the real project, open the dummy project and make the tweaks and save, then close the dummy project and return to the real project and the class is updated - though still locked. A small hassle but it works.

Again, thank you both for pointing me to this information.

lmd2