|
|
|
|
#1
07-09-2014, 07:55 AM
|
|||
|
|||
|
I understand Kinook does not support older releases of VBP so I posted here in the hopes others might be running with a similar environment and have some ideas.
It seems to me it is probably something simple as the command is getting formatted incorrectly. If the commands are formatted from the registry, I cannot find where. 
|
|
#2
07-09-2014, 08:02 AM
|
|||
|
|||
|
You might try overriding the location on the Options tab.
http://www.kinook.com/VisBuildPro/Ma...optionstab.htm
|
|
#3
07-09-2014, 08:06 AM
|
|||
|
|||
|
I have tried overriding the location to the 2010/2012 versions and it works. The problem is the sample script I sent was part of a far larger script that sets up a development environment. I won't be able to modify our "normal" build script. The small script I created because I could duplicate the issue and try to solve it without running the larger script.
How is the command for DEVENV.COM created? I tried searching the registry but I could not find it.
|
|
#4
07-09-2014, 08:19 AM
|
|||
|
|||
|
There is logic in the Make VS action to construct the command-line call. Apparently that logic in Visual Build v7 doesn't work with VS 2012, or perhaps there is a problem due to running in compatibility mode. Most likely, the only ways to resolve are to override the path or upgrade Visual Build.
|
|
#5
07-09-2014, 08:28 AM
|
|||
|
|||
|
The eval version of VBP (v8.7) worked.
I do appreciate the suggestions.
|
 |
| Tags |
| create , devenv , failed , process |
|
|
Hybrid Mode
