Rif.: Separate compiled code for many projects

[Raukho]

Hi,

is there a better way for me to separate compiled code for a lot of projects than opening every singe one and setting the check mark...
Like can i set the xml tag in the project file? Will it just separate the code after it's opened once?

The "problem" is our team is just now starting to use git (so they never cared about this setting) and now i'm here having to migrate a lot of very big projects, it often takes 3-4 minutes just to open the project. There has to be a better way than having to open every single one.

Thanks a lot for any ideas

[Basjong53]

Use the attached VI.

Disclaimer: It's not mine. I have found it on this forum, but I don't remember where unfortunately, so I cannot give credit.

[Raukho]

Thanks a lot, this looks really promising!

But I can't get it to work properly, maybe because a Sub-VI is missing. Would you mind uploading it again with all the Sub-VI's?

[billko]

---

@Raukho wrote:

Hi,

is there a better way for me to separate compiled code for a lot of projects than opening every singe one and setting the check mark...
Like can i set the xml tag in the project file? Will it just separate the code after it's opened once?

The "problem" is our team is just now starting to use git (so they never cared about this setting) and now i'm here having to migrate a lot of very big projects, it often takes 3-4 minutes just to open the project. There has to be a better way than having to open every single one.

Thanks a lot for any ideas

---

While this way would seem to be not efficient, it's probably the best way to do it to ensure that everything gets done correctly.  (Don't forget to "Mark existing items".)

[Basjong53]

---

@Raukho  ha scritto:

Thanks a lot, this looks really promising!

But I can't get it to work properly, maybe because a Sub-VI is missing. Would you mind uploading it again with all the Sub-VI's?

---

It uses a VI from the openG library. It is not really required, so you can simply delete that subVI and run the VI.

[Michael_Munroe]

The add-on Property Inspector 5.0 will load the project, find all VIs with Separate Compiled Code disabled, select all and replace the setting with true.  You can write a macro in under a minute to perform this sequence in a single click.  You can also write a macro to load a project, run the macro and close the project. Finally, you can write a macro to run the previous macro repeatedly for an unlimited number of projects. Just use parameters to pass the full project path from the top macro to the next macro. 

Here are the 3 macros:

Set Separate.pi5:

Search Separate Comp. Code 0

Select All

Edit Replace 1

Set Proj Separate.pi5:

Project Open %1

Call C:\YourPath\Set Separate.pi5

Project Close

Set Projects Separate.pi5:

Call C:\YourPath\Set Proj Separate.pi5 C:\YourPath\Proj1.lvproj

Call C:\YourPath\Set Proj Separate.pi5 C:\YourPath\Proj2.lvproj
Call C:\YourPath\Set Proj Separate.pi5 C:\YourPath\Proj3.lvproj

Call C:\YourPath\Set Proj Separate.pi5 C:\YourPath\Proj4.lvproj

[Raukho · Accepted solution]

Hi,

I ended up creating a quick flor with power automate. Was still an awful experience but better than doing all that manually!

Thanks for any help tho!