Installer Properties --> Registry: delete a key?

[battler.]

I mean so the user cannot find and remove the file/string/path whatever it happens to be.

Good point the ProgData folder is a hidden folder.  Thanks for letting me know they're not removed upon uninstallation.  However, that is how I put the folder there in the first place; using the installer, so it's likely to be removed upon uninstallation.  I'll have to try it.

Also, I read that the ProgData folder is "not always accessible".  Will the application will be denied from writing to the ProgData folder at any time during runtime?

Cheers.

[dan_u]

As stated before, if the config file is modified (by the running application for instance) then the uninstaller will not remove it (afaik).

---

battler. wrote:

Also, I read that the ProgData folder is "not always accessible".  Will the application will be denied from writing to the ProgData folder at any time during runtime?

---

Where did you read that? I'm not aware of such a limitation.

[battler.]

I create a new ProgApp folder using the LabVIEW installer, include an ini file in the folder. If I modify it the the OS will not remove it during unistallation? If I don't modify it (or anything ese in the folder it will remove it? Is that what you're saying?

I ready it in the LabVIEW 2009 Help documents. New VI in there called Get System Directory. They call is the Public Application Data folder (as one of the possible return values of the VI). I assume this is as Windows refer to it the Common AppData folder.

The LabVIEW help entry reads:

Public Application Data—Directory that contains data for system applications accessible to all users of the system. This directory is readable and sometimes writable.

Does anybody know when the Common AppData folder would not be writable? Would you agree this is what NI refer to as the Public Application Data?

[battler.]

system directory type specifies the type of directory you want LabVIEW to retrieve.

0	User Home—Directory that contains the personal files of the current user. This directory is a readable and writable directory accessible to a single user of the system.
1	User Desktop—Directory that contains files located on the desktop of the current user. This directory is a readable and writable directory accessible to a single user of the system.
2	User Documents—Default directory for saving the documents of the current user. This directory is a readable and writable directory accessible to a single user of the system.
3	User Application Data—Directory that contains data for the system applications of the current user. This directory is a readable and writable directory accessible to a single user of the system.
4	User Preferences—Directory that contains the preferences for the current user. This directory is a readable and writable directory accessible to a single user of the system.
5	User Temporary—Directory that holds temporary files for the current user. This directory is a readable and writable directory accessible to a single user of the system. You cannot change the path to this temporary directory.
6	Public Documents—Directory that contains documents accessible to all users of the system. This directory is readable and sometimes writable.
7	Public Application Data—Directory that contains data for system applications accessible to all users of the system. This directory is readable and sometimes writable.
8	Public Preferences—Directory that contains preferences common to all users of the system. This directory is readable and sometimes writable.
9	System Core Libraries—Directory that contains the libraries that come with the operating system. This directory is typically read-only to the standard user of the system.
10	System Installed Libraries—Directory that contains libraries a user installs on the system. This directory is typically read-only to the standard user of the system.
11	Application Files—Directory that contains files of applications installed on the system. This directory is typically read-only to the standard user of the system.
12	Boot Volume Root—Top-level directory used to start the system. This directory is typically read-only to the standard user of the system.

[dan_u]

---

battler. wrote:
I create a new ProgApp folder using the LabVIEW installer, include an ini file in the folder. If I modify it the the OS will not remove it during unistallation? If I don't modify it (or anything ese in the folder it will remove it? Is that what you're saying?

---

Yes, if I remember correctly that's how the uninstaller behaves.

---

battler. wrote:

I ready it in the LabVIEW 2009 Help documents. New VI in there called Get System Directory. They call is the Public Application Data folder (as one of the possible return values of the VI). I assume this is as Windows refer to it the Common AppData folder.

The LabVIEW help entry reads:

Public Application Data—Directory that contains data for system applications accessible to all users of the system. This directory is readable and sometimes writable.

Does anybody know when the Common AppData folder would not be writable? Would you agree this is what NI refer to as the Public Application Data?

---

I'm not using LV2009 yet, so I was not aware of this function. Sounds good though. Just see what it returns then you know whether it's the correct folder. I have no clue though under which circumstances the folder is NOT writable. Probably when logged in as guest?

[battler.]

---

dan_u wrote:

---

battler. wrote:
I create a new ProgApp folder using the LabVIEW installer, include an ini file in the folder. If I modify it the the OS will not remove it during unistallation? If I don't modify it (or anything ese in the folder it will remove it? Is that what you're saying?

---

Yes, if I remember correctly that's how the uninstaller behaves.

That's interesting behaviour.  Anyone else know about this?

---

battler. wrote:

I ready it in the LabVIEW 2009 Help documents. New VI in there called Get System Directory. They call is the Public Application Data folder (as one of the possible return values of the VI). I assume this is as Windows refer to it the Common AppData folder.

The LabVIEW help entry reads:

Public Application Data—Directory that contains data for system applications accessible to all users of the system. This directory is readable and sometimes writable.

Does anybody know when the Common AppData folder would not be writable? Would you agree this is what NI refer to as the Public Application Data?

---

I'm not using LV2009 yet, so I was not aware of this function. Sounds good though. Just see what it returns then you know whether it's the correct folder. I have no clue though under which circumstances the folder is NOT writable. Probably when logged in as guest?

---

Would be good to know when the AppData folder is not writeable, wouldn't it.  NI?  Anybody?

[rolfk]

---

battler. wrote:

Would be good to know when the AppData folder is not writeable, wouldn't it.  NI?  Anybody?

---

Well, come-on! Software engineering is also the ability to find such things yourself. And if you can't, the best place to ask this would be certainly a Vista developer or support forum, not a LabVIEW one.

Rolf Kalbermatter 

[battler.]

Listen to me Rolf.  Since when did you become the moderator of this forum?  I will leave NI to tell me what I should and should not ask on an NI forum.

It just became a LabVIEW (NI) problem when they provided the VI and the documentation, which is something I have paid for.

Do not tell me what I should or should not know.  FYI I am not, as the majority of LabVIEW users are not, a software engineer.

[rolfk]

---

battler. wrote:

Listen to me Rolf.  Since when did you become the moderator of this forum?  I will leave NI to tell me what I should and should not ask on an NI forum.

It just became a LabVIEW (NI) problem when they provided the VI and the documentation, which is something I have paid for.

Do not tell me what I should or should not know.  FYI I am not, as the majority of LabVIEW users are not, a software engineer.

---

I will in the future refrain from answering to any and all questions from you so you can keep your peace.

Rolf Kalbermatter

[smercurio_fc]

Congratulations, battler. Managed to revert back to your old habits, I see. I've been seeing your recent postings and have been amazed at your cordiality. Even wondered if you had a personality transplant. You managed to win back the favor of some veterans and professionals like Rolf. Only to blow it again.