The problem for us is that environment variables set by pre-build commands were no longer set when post-build commands were executed. Attached is a minimal project that demonstrates the problem.
In the workspace properties, we set an environment variable:
Set APPNAME=Hello
In the project's pre-build commands we set another environment variable which references the one from the workspace:
SET XMLFILE=%(APPNAME).xml
Then in the project's post-build commands we have a series of echo statements to generate an XML file. One example is here:
echo ^<Application name="%(APPNAME)"^> >%(XMLFILE)
In SlickEdit v14, the environment variables are set correctly and everything executes successfully. I used v14.0.2.2 with hotfix 26 to test this example project.
However, in SlickEdit v15 (I'm using v15.0.1.3 with hotfix 19) the problem is that the XMLFILE environment variable is not set when the post-build commands run, so to the operating system the command looks like:
echo ^<Application name="Hello"^> >
The command fails because the syntax is wrong (i.e. no file or device is specified for redirecting the output.)
However, the APPNAME environment variable from the workspace properties is set correctly, as shown in the echo command.
So it appears that environment variables set in the pre-build commands are not being carried forward into later build commands or are not actually being set in the first place.
I don't know if this is related to gawied's PATH problem or not, but it could be.
EDIT: I just now submitted a bug report about this issue.