Dll C# in installer for deployment in access VBA

Question

0.00/5 (No votes)

See more:

Hello.
I have a dll in C# built in VS2015 MS in Windows 7 that sends email using the SendGrid C# library. During development I had a reference in Access vba to the bin folder created by VS2015. It works as required. Next, I built an installer with VB2015, installed it in the same development computer, and changed the Access vba reference to the .tlb file in the installed directory. The Access application in the development computer continues working as required.

Now, in the production computer SO Windows 8 the installer runs with no problems and the reference to the .tlb in Access vba compiles. However when the functions depending on the dll are called, Access vba shows an error 429 ActiveX Object can't be created.

What I have tried:

In the production computer I was trying to register manually the dll using RegAsm.exe but it display an error saying the assembly or one of its dependencies were not found, with no more detail.
Dependencies are in the installer, as I can see them in the installation folder of the production computer and they are the same ones used in the development computer.

What other thing to do or check?

Posted 9-Nov-17 6:48am

Member 9616382

Updated 9-Nov-17 7:45am

Add a Solution

1 solution

Add a Solution

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)

Dave Kreskowiak · Answer 1 · 2017-11-09T07:45:00

Solution 1

The key here is in the error message: "the assembly or one of its dependencies were not found".

If you're using a 3rd party library .DLL in your .DLL code, you have to ship that 3rd party library with your .DLL in your installer.

Posted 9-Nov-17 7:45am

Dave Kreskowiak