Problem with GetEnvironmentVariable

[Nikolay Petrov]

the GetEnvironmentVariable method returns "Nothing" when used against a
environment variable, created by me.
I've tried using SET from the console, or "Environment Variables" in my
computer properties.
Tested on 2 PCs.

Whats the problem?

[Nikolay Petrov]

Also I can read some of the current system variables like "windir".

The example in MSDN also don't show my variable, but I can sse it using
SET from the command prompt

Example source:
' Sample for the Environment.GetEnvironmentVariables method
Imports System
Imports System.Collections

Class Sample
Public Shared Sub Main()
Console.WriteLine()
Console.WriteLine("GetEnvironmentVariables: ")
Dim environmentVariables As IDictionary =
Environment.GetEnvironmentVariables()
Dim de As DictionaryEntry
For Each de In environmentVariables
Console.WriteLine(" {0} = {1}", de.Key, de.Value)
Next de
End Sub 'Main
End Class 'Sample

[Ray Cassick]

Try restarting the PC after you add your vars into the properties area. I
don't think those are dynamic. They get read in when you boot up and I don't
think they get refreshed without a restart...

"Nikolay Petrov" <jo******@mail.bg> wrote in message
news:11**********************@g47g2000cwa.googlegr oups.com...

the GetEnvironmentVariable method returns "Nothing" when used against a
environment variable, created by me.
I've tried using SET from the console, or "Environment Variables" in my
computer properties.
Tested on 2 PCs.

Whats the problem?

[Herfried K. Wagner [MVP]]

"Ray Cassick" <rc******@nospam.enterprocity.com> schrieb:

Try restarting the PC after you add your vars into the properties area. I
don't think those are dynamic. They get read in when you boot up and I
don't
think they get refreshed without a restart...

It's possible to define environment variables in a batch file which will be
valid until the batch file is processed. I often follow this approach to
start tools which need certain environment variables without the need of
changing the whole system's environment variables.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>

[Nikolay Petrov]

I can see them, without doint restart using the SET command from the
console.
Also can assign new values, works just fine.
Except in my app.

[Ray Cassick]

Yes, but can you create them in one session (batch file) and see then in
another?

I just opened 2 command windows.. in one I typed 'set tester=me'. Ten in
that same window I typed set and was able to view it. In the second command
window I typed set it was not present. Seems to prove that env vars defined
in a batch files do not cross process boundaries.

Now, I created an env var named tester in my system properties (as a system
env var) and set its value. Once I hit apply I could open a command window
and type set and see it there..
"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in message
news:eM**************@TK2MSFTNGP12.phx.gbl...

"Ray Cassick" <rc******@nospam.enterprocity.com> schrieb:

Try restarting the PC after you add your vars into the properties area. I don't think those are dynamic. They get read in when you boot up and I
don't
think they get refreshed without a restart...
It's possible to define environment variables in a batch file which will

be valid until the batch file is processed. I often follow this approach to
start tools which need certain environment variables without the need of
changing the whole system's environment variables.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>

[Herfried K. Wagner [MVP]]

"Ray Cassick" <rc******@nospam.enterprocity.com> schrieb:

Yes, but can you create them in one session (batch file) and see then in
another?

No, but you should be able to see them in an application that is started
from within the batch file.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>