Can LabVIEW "read" Microsoft Windows Environment Variables?

[MikeMesolella]

Yup takes some work either way to write the code. Is a very good point!

I did provide the directions to get to the .NET API.

Only advantage of the Call Library Node Method I see is it's faster. But do you care if it takes 100 mS instead of 1 mS. For most people no. 

[rolfk]

---

@MikeMesolella wrote:

Yup takes some work either way to write the code. Is a very good point!

I did provide the directions to get to the .NET API.

Only advantage of the Call Library Node Method I see is it's faster. But do you care if it takes 100 mS instead of 1 mS. For most people no. 

---

Some people care about 1.1ms vs 1.0ms. I find that artificial, but 1ms to 100ms definitely is something I wouldn't dismiss as insignificant. 😀

But my main point is, if you don't know about DLL function calling and its particular possible problems, .Net is the best solution for you. But if you know about these things quite a bit, I would take direct Win32 API calls any moment of day or night before going .Net. 😁

[billko]

---

@rolfk wrote:

---

@MikeMesolella wrote:

Yup takes some work either way to write the code. Is a very good point!

I did provide the directions to get to the .NET API.

Only advantage of the Call Library Node Method I see is it's faster. But do you care if it takes 100 mS instead of 1 mS. For most people no. 

---

Some people care about 1.1ms vs 1.0ms. I find that artificial, but 1ms to 100ms definitely is something I wouldn't dismiss as insignificant. 😀

But my main point is, if you don't know about DLL function calling and its particular possible problems, .Net is the best solution for you. But if you know about these things quite a bit, I would take direct Win32 API calls any moment of day or night before going .Net. 😁

---

And if you're not comfortable using any of these methods, System Exec works just fine.