Wrong "Current VI's Path" in LV 2009

[battler.]

Wrong.

[tst]

OK, I'll bite.

Right.

[battler.]

Tst your solution got a Kudos.

[tst]

Here's a tip for a better life:

First, try searching for an answer. Really try. And read the content.

Then, IF you didn't find an answer, you can post a question.

A whole question.

Not "wrong" or "this is stupid" or any of the other similar things you've done.

Be polite and respectful and you might actually get answers.

[parthabe]

---

tst wrote:
I should point out that LV 2009 also has a new VI (I believe it's called "Application Directory" and is in the file constants palette) which returns the folder of the application, similar to what the image Ben posted shows. In the EXE it returns the EXE's folder and in the IDE it returns the project or top level VI folder. If you do want the folder, you should use that from now on.

---

Is this different from the Application Directory Path property?

Because I remember that this property returns the EXE's folder in the run-time environment, but returns the LabVIEW.exe's folder in the IDE.

I feel that NI could have probably changed the behaviour of this property instead of adding one more file function.

[battler.]

It works for me!

[parthabe]

What works for you?  Can you be a bit more clear?

[muks]

---

What works for you?  Can you be a bit more clear?

---

And mark the solution?

[battler.]

Application path directory constant works fine during development and also as an executable.

[tst]

---

parthabe wrote:

I feel that NI could have probably changed the behaviour of this property instead of adding one more file function.

---

What about backward compatibility? Some people might be relying on the property returning the LabVIEW folder.