Regsvr32 ServerDll error

Question

4.00/5 (1 vote)

See more:

Hello,,

VB

retVal = Shell("Regsvr32.exe c:\temp\comcslibrary.dll", 1)

I have the above statement in may vba code. And it giving me the error as....

c:\temp\comcslibrary.dll was loaded, but the DllRegisterServer entry point was not found. This file can not be registered.

The particular dll has been developed in c#.Net And I need to invoke the function written in it, in my vba code. How to get rid of this error???

Posted 6-Aug-12 23:38pm

comred

Updated 7-Aug-12 2:19am

ZurdoDev

v2

Add a Solution

Comments

[no name] 7-Aug-12 7:42am

You cannot. It's not an ActiveX DLL so it does not need to be registered.

ZurdoDev 7-Aug-12 8:19am

Can't you just add it as a reference in VBA in project properties instead?

comred 8-Aug-12 3:03am

for my local machine it is fine. But what if, I distribute it among my clients in diferent location? they also need to go in tools-->Reference and then checking that dll right.. because of this my vba code may exposed to him. and I don't want it.

ChandraRam 8-Aug-12 7:00am

You will anyway need to distribute the DLL file. So long as Excel is able to find it in the path, it should work fine. Just add the function declarations your VBA project, with instructions when distributing, to place the DLL file in the same folder as the Excel file.

Maciej Los 4-Sep-12 16:29pm

@ChandraRam, my virtual 5!

ZurdoDev 8-Aug-12 7:52am

As ChandraRam mentioned, you just need to include the dll because the project properties will be expecting the dll on the client machine also.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)