OK, I'm sure I'm not the only one that needs to do this. We have a product that has about 18 different EXE's with it. One DLL for the object based stuff and 36 Language DLL's that support English and Traditional Chinese. So we have about 55 exes and dll that make up a product. Sheesh, I know it's ugly, but we can't change it right now.<br><br>The problem is trying to do a build for this thing. Right now I have it running out of a batch file, but when you make the programs from the command line with VB6, the revision doesn't get incremented. I even have the project files checked out of SourceSafe before I do the build. That's in the batch file too! However, Microsoft says that there is a bug in the command line for VB6 where it won't increment the revision in the VBP file.<br><br>This has a cascaded effect apparently, because when I package and deploy the application, since the version number hasn't changed, the new EXE's and DLL's don't install because it thinks they are the same version.<br><br>Now for my question. Does anyone know of a MAKE or BUILD utility for Visual BASIC that will allow you to maybe graphically pick the files you want to build and specify an output directory, etc for Visual BASIC?<br><br>The batch file works fine, however it's a real pain in the you know what to maintain.<br><br>Any and all comments or ideas welcome!<br> <p>Steve Meier<br><a href=mailto:tribesaddict@swbell.net>tribesaddict@swbell.net</a><br><a href= > </a><br>
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Building multiple EXE's for a product...
- Thread starter Snaggs
- Start date
Karl Blessing
Programmer
well since its VB6, I assume that each exe is its own project?, if so you can add every project onto a single group in VB, then just build them all by selecting all the projects in the project manager. thats one way if all your exe are made from different projects, also a good way to debug activex's inside your exes, by adding their projects as well you can jump to the exact line of the error, throught the exe and throught the activeX. <p>Karl<br><a href=mailto:kb244@kb244.8m.com>kb244@kb244.8m.com</a><br><a href= </a><br>Experienced in , or have messed with : VC++, Borland C++ Builder, VJ++6(starting),VB-Dos, VB1 thru VB6, Delphi 3 pro, Borland C++ 3(DOS), Borland C++ 4.5, HTML,Visual InterDev 6, ASP(WebProgramming), QBasic(least i didnt start with COBOL)
- Thread starter
- #3
Thanks for the reply Karl! However it's not quite that simple. That would take care of the versioning for the EXE's but not for the language DLL's. There is some file copying that goes on in the background. It copies resource files into a common directory from either an English or Chinese directory, then it builds the project. It does this each time for as many languages as we have.<br><br>I'm trying to get an automatic build.<br><br>Update... I did go out to Microsofts site and download their Visual Installer. It's a nice setup program. Much nicer than the P&D Wizard. Gives you much more control over what you can do and how you can package the stuff. However, as far as I know it still won't help me with the build.<br><br>I also ran across a freeware tool that version stamps the exe or dll. However, this isn't any good either because if the product gets built on a different machine, the version numbers will be out of sync. I just don't like the idea that the version number doesn't get updated in the Project file. I guess I'll have to write a little app that goes in there and does that for me, as much as I was trying to avoid doing that.<br><br>Thanks again, <p>Steve Meier<br><a href=mailto:tribesaddict@swbell.net>tribesaddict@swbell.net</a><br><a href= > </a><br>
Karl Blessing
Programmer
I dont know how much time you have left, but have you considered writing a instalation/build program to do all the stuff you want for you? I'm writing an instalation program for WebSaras(you probally never heard the name since, alot of states put up their own logo and name, when we sell it to different states) since its kind of simple as far as the approach goes (get hardware when Install, Update, Cancel, type features are put in) I dont think I know much more to help you. I would think that writing yourself a program to do the task would helpyou with maximum flexibility. <p>Karl<br><a href=mailto:kb244@kb244.8m.com>kb244@kb244.8m.com</a><br><a href= </a><br>Experienced in , or have messed with : VC++, Borland C++ Builder, VJ++6(starting),VB-Dos, VB1 thru VB6, Delphi 3 pro, Borland C++ 3(DOS), Borland C++ 4.5, HTML,Visual InterDev 6, ASP(WebProgramming), QBasic(least i didnt start with COBOL)
- Thread starter
- #5
Yeah, That's what I was thinking. I didn't really want to reinvent the wheel if someone knew of something out there already. But I guess that I'll be breaking new ground on it soon.<br><br>Thanks again, <p>Steve<br><a href=mailto:tribesaddict@swbell.net>tribesaddict@swbell.net</a><br><a href= > </a><br>
Karl Blessing
Programmer
normally the best products for your own products are you own handlers, or modifications of other handlers to suit your need, like when my boss wanted to make a VPN, through FTP protocals(to start off with) he didnt want to buy an activeX , he wanted to buy the source code so I could modify it , and strip it down to size, which became just using raw winsock commands. <p>Karl<br><a href=mailto:kb244@kb244.8m.com>kb244@kb244.8m.com</a><br><a href= </a><br>Experienced in , or have messed with : VC++, Borland C++ Builder, VJ++6(starting),VB-Dos, VB1 thru VB6, Delphi 3 pro, Borland C++ 3(DOS), Borland C++ 4.5, HTML,Visual InterDev 6, ASP(WebProgramming), QBasic(least i didnt start with COBOL)
- Thread starter
- #7
OK, I had to revert to something that would change the Revision number for me. While this code works for me, use it at your own risk.<br><br>Option Explicit<br><br>Public Sub Main()<br> Dim strBuffer As String, strNewString As String, strFilename As String<br> Dim intRevision As Integer, intFileHandle As Integer<br> Dim lOffset As Long<br> <br> On Error GoTo MainErr:<br> <br> strFilename = Command<br> <br> If strFilename = "" Then<br> MsgBox "Usage: AutoRev <Project.VBP>"<br> Exit Sub<br> End If<br> <br> If Dir$(strFilename) = "" Then<br> MsgBox "File not found: " & strFilename<br> Exit Sub<br> End If<br> <br> intFileHandle = FreeFile<br> <br> Open strFilename For Binary As #intFileHandle<br> <br> strBuffer = String(LOF(intFileHandle), 0)<br> Get #intFileHandle, 1, strBuffer<br> <br> 'Make sure we want to auto-increment.<br> lOffset = InStr(1, strBuffer, "AutoIncrementVer=1"
<br> If lOffset > 0 Then<br> <br> lOffset = InStr(1, strBuffer, "RevisionVer="<br> strNewString = Mid$(strBuffer, 1, lOffset + 11)<br> <br> intRevision = CInt(Mid$(strBuffer, lOffset + 12, InStr(lOffset + 12, strBuffer, vbCrLf) - (lOffset + 12)))<br> intRevision = intRevision + 1<br> <br> 'Make sure we stay within the limits of VB's versioning.<br> If intRevision > 9999 Then<br> intRevision = 0<br> End If<br> <br> 'Build the new project file to write.<br> strNewString = strNewString & CStr(intRevision) & Mid$(strBuffer, InStr(lOffset + 12, strBuffer, vbCrLf))<br> End If<br> <br> 'Write the updated information back to the VBP.<br> Put #intFileHandle, 1, strNewString<br> <br> Close #intFileHandle<br> <br> Exit Sub<br> <br>MainErr:<br> MsgBox "Error #" & Err.Number & vbCrLf & Err.Description<br>End Sub <p>Steve<br><a href=mailto:tribesaddict@swbell.net>tribesaddict@swbell.net</a><br><a href= > </a><br>
<br> If lOffset > 0 Then<br> <br> lOffset = InStr(1, strBuffer, "RevisionVer="<br> strNewString = Mid$(strBuffer, 1, lOffset + 11)<br> <br> intRevision = CInt(Mid$(strBuffer, lOffset + 12, InStr(lOffset + 12, strBuffer, vbCrLf) - (lOffset + 12)))<br> intRevision = intRevision + 1<br> <br> 'Make sure we stay within the limits of VB's versioning.<br> If intRevision > 9999 Then<br> intRevision = 0<br> End If<br> <br> 'Build the new project file to write.<br> strNewString = strNewString & CStr(intRevision) & Mid$(strBuffer, InStr(lOffset + 12, strBuffer, vbCrLf))<br> End If<br> <br> 'Write the updated information back to the VBP.<br> Put #intFileHandle, 1, strNewString<br> <br> Close #intFileHandle<br> <br> Exit Sub<br> <br>MainErr:<br> MsgBox "Error #" & Err.Number & vbCrLf & Err.Description<br>End Sub <p>Steve<br><a href=mailto:tribesaddict@swbell.net>tribesaddict@swbell.net</a><br><a href= > </a><br>
Karl Blessing
Programmer
um, if you are refering to the distribution packer, Visual Basic comes with that. <p>Karl<br><a href=mailto:kb244@kb244.8m.com>kb244@kb244.8m.com</a><br><a href= </a><br>Experienced in , or have messed with : VC++, Borland C++ Builder, VJ++6(starting),VB-Dos, VB1 thru VB6, Delphi 3 pro, Borland C++ 3(DOS), Borland C++ 4.5, HTML,Visual InterDev 6, ASP(WebProgramming), QBasic(least i didnt start with COBOL)
- Thread starter
- #10
The link for it is here. It's like the 3rd or 4th item down on the list.<br><br><A HREF=" TARGET="_new"> the description for it:<br><br>Visual Studio Installer 1.0<br> <p>Steve<br><a href=mailto:tribesaddict@swbell.net>tribesaddict@swbell.net</a><br><a href= > </a><br>
- Status
