Re: DLL works when built from VB IDE but not from command line

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

As I said "I wonder if you have a stack overflow?". VB6 allocates 1MB stack
by default, C++ a lot less, when building. Try increasing the stack size
massively when you link.

I have a case where VB6 calls a lot of PL/I. Since PL/I is stack-intensive,
we needed to ask VB6 to use a 10MB stack, otherwise the application crashes.

"Richard" <Richard@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:544F0A47-7D26-414C-9B68-6686D94E14B6@xxxxxxxxxxxxxxxx
> We have a similar problem here. If the project is a C++ managed project,
> then project references are simply ignored when the build occurs on the
> command line. Works fine in the IDE, but not on the command line.
>
> Is there a resolution for this?
>
> Richard
>
> "Mark Yudkin" wrote:
>
>> I wonder if you have a stack overflow, or other corruption, in the
>> hosting
>> EXE? You mention .NET. Are you trying to call your VB6 DLL from a .NET
>> environment? If so, you may have an interop issue (==> .NET forum).
>>
>> "P Abramowitz" <PAbramowitz@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:6C6A30DA-BA76-4F4D-802C-A2410B760C05@xxxxxxxxxxxxxxxx
>> > We have an application containing many VB6 DLLs that we've had for many
>> > years. Recently we started ported some of them to .NET. We started
>> > noticing
>> > some strange behaviour with 2 of our old VB6 DLLs recently. When we
>> > build
>> > them from the command line (as our batch builder does) some of their
>> > classes
>> > do not work in the application. If we build them in the VB IDE, they
>> > will
>> > work fine. If we then rebuild them from a command line they stop
>> > working
>> > correctly. This is a recent problem - building from the command line
>> > has
>> > worked for many years. It's not a registration issue - running
>> > regsvr32
>> > has
>> > no effect. The command line is nothing more than "vb6.exe /m <project
>> > name>". Any ideas?
>>
>>
>>


.

Relevant Pages

  • VB6 Command Line compile crashes but IDE compile is okay
    ... In 2006 I had no trouble compiling my VB6 application from the command line, ... I can compile from from the IDE. ...
    (microsoft.public.vb.general.discussion)
  • Re: Using Microsoft Chart Control in dotnet
    ... I created a VB6 project and this worked without any problems ... After running the Dependency Walker tool on the MSCHRT20.OCX file in the ... C:\Windows\SysWow64\ folder I found that there are two files which can not ... In the command prompt, type "depends" command and press enter. ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Re: What is the status of VB6 & DOT.NET ?
    ... Microsoft's Upcoming Vista To Support Legacy VB6 Apps ... converts and people who like using the command line. ... whether VBScript and the WSH will still be available. ...
    (comp.lang.basic.visual.misc)
  • Re: Could not execute C2.EXE
    ... I checked other env variables in case VB6 used them. ... My gut feelng is I am not breaking any of the limitations of VB6. ... Computer is relatively new - Dell Optiplex GX620 with 2 processors. ... And, just for grins, what about executing C2 from the command line? ...
    (microsoft.public.vb.general.discussion)
  • Re: Read MAG tape to disk
    ... > I have a PL/I application that write data to a mag tape that is ... > mounted using the following command: ... length and RMS is involved in the process of writing the output records. ...
    (comp.os.vms)