Best folder location(s) for application ini

[GriffinRU]

Cool, it is a view point my friend.

To acomplish our jobs you create extra data to overcome programming limitations, I use windows tools for my needs. As result -> very small foot print in bits.

-Artur

[John_P1]

I know we should probably just agree to disagree and move on, but I couldn't resist...

---

@GriffinRU wrote:

Sure, multiply your foot-print!!!

---

We're talking about a config file that for most applications will fit within a single disk sector.

---

@GriffinRU wrote:

Not to go too far into how to make it editable (I can think of couple at least), think of background service with system rights (created when you were admin) to do your dirty laundry...

---

Are you describing creating a background service just to handle writing to your config file (which Microsoft already allows you to do easily using their suggested directories)?  How much disk space does this background service take?  

---

@GriffinRU wrote:

I am assuming that LabVIEW has a built-in function to get Windows enviroment variables and adjusts to them on-the-fly without you programming how to handle that.

---

I'm not sure if you were being sarcastic or not, but LabVIEW has exactly this:

---

@GriffinRU wrote:

If you ask were to store your data then you should follow recommendations from above but if you seasoned programmer than you should be efficient in using bits.

---

I disagree.  The kind of hacky workarounds people sometimes incorporate to make very marginal improvements in areas that don't really matter very often do more harm than good (even if it makes perfect sense to the original developer, consider the poor guy who has to inherit the software and then figure out all of the non-standard approaches that were taken).

---

@GriffinRU wrote:

As long as your code is simple and file location is trivial and follows LabVIEW way, you should be 99% closer to get happy customers.

---

Using the intended WIndows directory is simple and trivial--though I guess it doesn't really follow the LabVIEW way.  Despite my appreciation for LabVIEW, I wouldn't necessary say that following its lead in every case is going to lead to happy customers (as a relevant example, customers tend to not like numerous poorly-documented background services running on their computers).

Best Regards,

[GriffinRU]

John,

I will disagree, no more bits!

-Artur