|
Funny thing is that it appeared to fix itself when I exited that Visual Build Pro application and restarted it. The INCLUDE enviroment variable appeared correctly.
This whole thing started because I have setup a scheduled task to run during the night to perform a build on our product. Sometimes that task never really starts and we're not sure why. Last night was an example.
So, today, after last nights failure, I attempted to start it from the IDE and that is when I had the problem. One suspicious thing is that the IDE was already loaded and my user was already logged into the machine over night. I'm wondering if running it as a scheduled task somehow caused my currently running VB Pro IDE to have the wrong environment and that is why it was failing and fixed itself when I reloaded the IDE.
|