Problem calling .NET 2.0 dll from VB6 on Win2000Pro machine

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Anders Nilsson - 25 Apr 2006 09:45 GMT

I have a problem getting following error message when calling a .NET 2.0
component from my VB6 code on a Win 2000 Pro machine (SP4).

"Run-time error '429'
ActiveX component can't create object"

Doing the same on an XP machine works just fine.
Doing the same calling the same component using .NET 1.1 works fine.

The component is installed using an msi installation created by VS2005.

Any help is welcome!

Signature

Kind Regards,
Anders Nilsson
Kvadrat AB

Reply to this Message

vomacka@gmail.com - 27 Apr 2006 21:29 GMT

Anders,

Try using the fuslogvw.exe program that came in the .Net 2.0 SDK to
view the errors that happen at assembly load time. My guess is that
you'll see that your program is using the 1.1 assembly manager to try
to load your 2.0 assembly. It could be other things as well. The fuslog
will show you where it found your assembly and what config files, if
any, it read during the load.

Reply to this Message

Richards - 23 May 2006 20:02 GMT

I have a similar problem.

I built a DLL file using .NET Studio 2003 on a WIN XP machine. This DLL
referenced by a legacy VB6 application. This combination works fine on my WIN
XP machine. When I try to run it on a WIN 2000 machine, I get nothing -
except the hour glass for a second and the chime.

Any ideas?

Thanks,

Richard

Reply to this Message

Richards - 23 May 2006 22:31 GMT

More information from the lab:

1) I tried using RegAsm on the DLL created by .NET - I got an error message
saying it's not a real .NET assembly

2) I suspect this works on my XP machine because this is the machine where I
built the DLL. Perhaps .NET studio is doing some sort of registration that is
not duplicated when I install on the WIN 2000 machines.

Any help will be appreciated.

Richard

Reply to this Message

Richards - 24 May 2006 19:54 GMT

SOLUTION FOUND:

The ActiveX DLL I built with .NET is not a .NET assembly. It is just a
regular ActiveX DLL that happens to have been built using .NET studio. RegAsm
has no effect on it.

My problem was that I was building in DEBUG mode. The VB6/ActiveX bundle as
an installed application on my office computer because it still had access to
.Net components. When installed on a computer without these items, it could
not run.

The solution was to build the DLL with its .NET project properties set to
"Release Minimum Depencencies". This initially caused some new link errors,
but these can be dealt with via other project properties.

Thanks to everyone who posted helpful information elsewhere on this board.

Richard

Reply to this Message

Problem calling .NET 2.0 dll from VB6 on Win2000Pro machine

Free Magazines