Going crazy - pls help!

Ok, so I have a DLL written in VB.NET for use in a VB6 app. The DLL was not written or compilied on my PC, but does work properly on it. I've packaged the VB6 app and the .NET DLL using .NET - creating a merge mod for the DLL and added COM registration for it. When testing on another PC have run into problems. The DLL is getting registered (I think - there are entries in the registry for it) but when trying to run the app, I am getting the 429 Active X error.

Anyone have any ideas how to fix or at least find the cause of the problem? I'm going nuts trying to figure it out! :confused:

Any suggestions would be greatly appriciated!

Is the .NET DLL referencing something that isn't installed on the destination computer? Is the .NET framework installed on it? Are you sure it's the .NET DLL that isn't instantiating, or could it be some other referenced object?

The .NET Framework is install on the PC. I have checked all the other .dll's and .ocx files required by the DLL and the EXE.

I'm positive it's the .NET dll and just to be sure built a little program that only calls a class w/in the .NET DLL and I also recieved the 429 error.

Its almost as if though it appears registered its not???

Have you release the correct files ? For instance the interop files. Is it the same version of the .Net framework ?

Both PC's have the .NET Framework v1.1.4322 on them.

I can't speak about the interop files cause I'm not sure what you are talking about?