Why the Project.Close() method does not start compilation like when manually closing the project?

[bienieck]

I have some project where all the code has separate compiled code. When I open this project manually and then close it, LV starts compiling LV compiled object cache for this project.

I tried to do the same programmatically. So, I prepared a simple VI (see attachment) and I was expecting that the Project.Close() method will trigger compilation as when closing manually. However, the cache is not compiling.

So, why the Project.Close() method does not start compilation like when manually closing the project? Why there is no consistency? How to automate LV compiled object cache creation?

[santo_13]

Just curious, why not regular mass-compile?

[bienieck]

---

@santo_13 wrote:

Just curious, why not regular mass-compile?

---

Can I mass-compile a project or it has to be a whole directory?

[santo_13]

I couldn't find a property node/invoke node to mass-compile the project but there is right-click option in the project explorer

[Kyle97330]

Could you use code like this to iterate through your entire project hierarchy to compile it all?

You'd probably want to add some restrictions so you don't compile things you don't want to, i.e. things in vi.lib

[bienieck]

I tried this code but the strange thing is that LV compiled code cache is not changing.