Martin Sebor wrote:
Andrew Black wrote:
Greetings Farid.
I checked the provided test case again on my local installation, and
discovered that it does not replicate the issue.
After further digging, I have found that the problem seems to have
been the use of the %G or %H variable in a for loop prior to invoking
devenv. This was worked around by using the SETLOCAL/ENDLOCAL
directives.
As batch scripts alter their environment unless the SETLOCAL command
is used, I had been reducing my test case in an environment where
these variables were undesirably set.
So is the original problem now resolved?
Martin
Kinda.
The glue script now works (and making the variables local I believe to
be a positive change), but the observed issue of stray environment
variables throwing the sanity test script off probably should be looked
into at some point.
--Andrew Black
