Kinook Software Forum

Go Back   Kinook Software Forum > Visual Build Professional > [VBP] Third Party Tools

Reply
 
Thread Tools Rating: Thread Rating: 2 votes, 5.00 average. Display Modes
  #1  
Old 12-29-2004, 11:49 AM
ecorcoran ecorcoran is online now
Registered User
 
Join Date: 12-29-2004
Posts: 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?
Reply With Quote
  #2  
Old 01-04-2005, 03:10 PM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 6,003
The Make VB6 action does not determine the executable filename, it ultimately invokes the VB6 compiler on the VBP to generate it.

See the attached example which demonstrates this (extract the files to a folder and run the TestBuild.bld file, which builds a basic ActiveX exe project with a different exe name than the project name [which is specified in the VBP file]).

If you are not seeing this behaviour, please post or send us the .bld file and the .vbp file in question and we'll take a look.
Attached Files
File Type: zip sample.zip (3.7 KB, 929 views)
Reply With Quote
Reply

Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



All times are GMT -5. The time now is 09:08 PM.


Copyright © 1999-2023 Kinook Software, Inc.