Would it have anything to do with this bug in the .NET framework? http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=326163
On May 12, 5:18 pm, Ruben Willems <[email protected]> wrote: > Hi > > I can not remember anything changed from head, but will look into this. > Keeping you posted ... > > with kind regards > Ruben Willems > > On Tue, May 12, 2009 at 8:37 AM, Alister Hatt <[email protected]>wrote: > > > > > Correct. The values are fine, the name is changed. Some more details > > below. > > > E.g. > > > I have a Windows XP system level environment variable > > MY_VAR=SOME_VALUE > > > In 1.4.4 when running an Exec task or Nant script, the environment > > variable will come out as: > > > my_var=SOME_VALUE > > > In 1.4.0 comes out as: > > > MY_VAR=SOME_VALUE > > > On May 12, 4:31 pm, Ruben Willems <[email protected]> wrote: > > > Hi > > > > just to get the facts : > > > > 1.4.0 has environment variables like CCNetLabel > > > 1.4.4 has environment variables like ccnetlabel > > > > correct? > > > > with kind regards > > > Ruben Willems > > > > On Tue, May 12, 2009 at 8:12 AM, Alister Hatt <[email protected] > > >wrote: > > > > > Hi, > > > > > I am experiencing a problem with ccnet 1.4.4x that seems to be causing > > > > all my system environment variable names passed to any CC projects to > > > > appear in lower case. I confirmed this case by writing a small script > > > > to output all the environment variables to the console. Upon reverting > > > > to ccnet 1.4.0 the problem goes away.
