#1
|
|||
|
|||
Make VB6 Action uses Project Name as Executable Name
I am using the Make VB6 action to build a VB6 project. The Project Name and the executable to generate are not named the same. The Visual Basic Project is named: FS_Debug. Inside the Visual Basic project file, the executable name to generate is: fsDebug.dll (ExeName32="fsDebug.dll").
When Visual Build Pro builds the project, the executable that is generated is named: FS_Debug.dll. The executable file should be: fsDebug.dll It appears that Visual Build Pro does not recognize the ExeName32 property. Is it possible to override this behavior? |
|
|