Home/ Questions/Q 7040383
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T01:54:42+00:00

This has caused me a day’s worth of work at this point. In visual

  • 0

This has caused me a day’s worth of work at this point. In visual studio I can add a reference to a custom-made .dll file. Once the reference has been added, I can call the .dll file:

someClass_inDll sc = new someClass_inDll();
sc.someVoid_in_dll();

Simple, right? No assembly use, invoking etc. needs to be done. I would like to be able to do this exact same thing using CodeDom! So, assume I have a custom .dll file (already made and on my hard drive), I have been adding the full path to said dll file to the list of codedom references. However, the actual .dll file is not being compiled with my project (as it is with visual Studio).

Can someone please tell me why this is? It’s making no sense to me what so ever.

I do NOT want to add the .dll file as an embedded resource because the only way I could call functions in the dll file would be to invoke it which is something I’d rather not do for personal reasons.

I really appreciate the help everyone!

Thanks,
Evan

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I am not sure I understand what you are asking, but here goes…

    Visual Studio is copying all of your references into the output directory that are set to “Copy Local” in your .proj file AFTER compilation. The compiler itself is not concerned with the deployment of your dependencies, this is what msbuild is for.

    So, when you add a reference to the CompilerParameters of your provider, it will use the reference to build the executable, but you will have to copy it yourself.

    • 0