Re: Application Error when starting

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: LisaConsult (lisaconsult_at_online.nospam)
Date: 11/02/04


Date: Tue, 2 Nov 2004 09:03:03 -0800

No, PolarZipLight is a 3rd Party DLL. We all installed it from the same
install program. The file is a COM DLL originally used in VB6. We are using
different versions of VS.NET (one is enterprise, one is just VB.NET
standard). You see, I believe there is something in the import of a Com
Object into the project through VS.NET that must be different since by
default one comes in as AX, the other as Interop. Until I get a resolution,
I'm including both DLLs in the build, but this really is not a long term
solution. Thanks.

"[MSFT]" wrote:

> Is AXPolarZipLight also a project from your team? I suggest you may strong
> name it. And then remove the reference and add again. Such a problem may be
> related to that you have multiple version of AXPolarZipLight.
>
> Luke
>
>



Relevant Pages

  • Re: About protected memory in COM(in-process)
    ... This in-process COM DLL was initially used from VB6 and it has worked ever ... It has never ever been any kind of problems with this COM dll. ... For about 7 month ago a C# asp.net webb application was deloped where this ... a VARIANT type that assumed that only one kind of VARIANT was being ...
    (microsoft.public.vc.mfc)
  • General DLL Questions - Best Practices? Suggestions? Comments?
    ... So we develop and maintain several applications used by several people ... rewrites of all the VB6 apps. ... The VB6 executables are all stored in a network folder, ... runs regsvr32.exe for each dll. ...
    (microsoft.public.dotnet.general)
  • Re: Problem with Multithread in VB6
    ... Events get raised by this DLL on their own threads ... In a VB6 client application, if I'll create an object "WithEvents" and write ... Dim frmMainForm As DispMain ... ' PublicNotCreatable) displays the main user interface ...
    (microsoft.public.vb.com)
  • Re: huge array
    ... VB6 due to lack of support. ... immensely since it was first released, and the learning curve now is far ... See above - the converter box is the .NET DLL which is exposing a COM ...
    (microsoft.public.vb.general.discussion)
  • Re: Register TLB
    ... The .net DLL was created and compiled with the "COM visible" option, ... Although the .DLL file appeared to be also registered, vb6 refused to ... So, I am left with having to reference the .TLB file, ... There didn't seem an option for generating a dependency file in vb.net, ...
    (microsoft.public.vb.general.discussion)