Unable To Register A DLL For Use In VB.NET Under Windows 7

Picture0004.pngPicture0004.pngPicture0004.pngPicture0004.pngPicture0004.pngPicture0004.pngHello Experts -

I've spent about 5 hours trying to register a COM DLL in VB.NET.

This is admittedly a new machine for me. Regsvr32 says it can't find the binary.

See the attached snapshot.

I wonder if there might be some special level of security that is preventing me from doing the registration function. I've been thru the Command Prompt with Administrator rights.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David Johnson, CDRetiredCommented:
If it is a 32 bit .dll on a x64 system check the c:\windows\syswow64 folder
gbmcneilAuthor Commented:
Well, thanks for responding Dave.

I have several DLLs to register. The one cited above (Metalib.dll) was able to be register by moving it into C:\Windows\SysWoW64.

But, I tried the next DLL, and it wouldn't fly by putting into SysWow64.

So, after a momentary feeling of success, I'm once again stumped.

What I am getting at this point is...

The module "fldpack.dll" was loaded but the entry point "DllRegisterServer" was not found.

Are there know differences in "regsvr32.exe"?

gbmcneilAuthor Commented:
If the remaining DLLs are not COM DLLs, can they be accessed by VB.NET without "Adding a Reference"?
Exploring ASP.NET Core: Fundamentals

Learn to build web apps and services, IoT apps, and mobile backends by covering the fundamentals of ASP.NET Core and  exploring the core foundations for app libraries.

David Johnson, CDRetiredCommented:
why don't you just add a reference?
gbmcneilAuthor Commented:
I've tried to add a reference.  That doesn't work because the Reference Function seems to be looking for a COM DLL.
gbmcneilAuthor Commented:
I've added a number of functions in a separate Module.

When an attempt to is made to use one of these functions, I get a badimage error.

I think that has something to do with defining the project as 64 bit verses 32 bit or all types.

Although I don't know where my app is defined as one or the other.

gbmcneilAuthor Commented:
In short, I think that somewhere my app has been defined as 64-bit, and I have been trying to register/use some non-COM 32-Bit DLLs.

Dave - Do you know where VB.Net defines the type of project (32-Bit, 64-Bit, or both) being developed?
Under the Compile tab of the Project properties; e.g. -Capture.PNG

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
gbmcneilAuthor Commented:
You are right, Dave. However, so not as to cause any further conflict, it seems that "x86" is the correct choice.

In short, VB.NET is saying that if you want to have a 64-bit application, all the functions in Dlls have to be 64-bit. And, if you try to register a 32-bit DLL in a pre-defined 64-bit project, VB.Net isn't going to participate.

Thanks very much for your help. Case closed.
gbmcneilAuthor Commented:
Thanks again for your help, Dave.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic.NET

From novice to tech pro — start learning today.