Import mono assembly or .net assembly

Question

0.00/5 (No votes)

See more:

Hi,

I have 2 DLLs, 1 is for Windows only (uses some Windows specific DLLs which are not supported by Mono) and 1 is for Mono. The method prototypes of those DLLs are all the same.
If Mono is detected the LJUDMono should be imported, else LJUDWin. And I'd like to do it statically with DLLImport.

Any suggestions? Resources?

To do it dynamically I found this article Fast late-bound invocation through DynamicMethod delegates[^].

Posted 13-Oct-11 1:44am

Member 7833626

Add a Solution

2 solutions

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)

Mehdi Gholam · Accepted Answer · 2011-10-13T02:10:00

Solution 1

Why don't you just deploy the two versions in different setups, obviously you will know which platform you will be running on so just package your files accordingly.

Posted 13-Oct-11 2:10am

Mehdi Gholam

Comments

BobJanova 13-Oct-11 9:33am

Giving this a 5 for being the simplest and best approach in most cases.

Mehdi Gholam 13-Oct-11 9:36am

We like simple things, programming is complex enough :)

BobJanova · Accepted Answer · 2011-10-13T02:53:00

You can't do it statically, almost by definition (the choice you are making is a runtime one). The simple solution is to deploy one DLL, and make it the appropriate one for the platform, as Mehdi suggests. If for some reason you can't do that, the best approach is probably a plugin based one whereby you choose which assembly to load at runtime, and have each assembly have a class which implements ILJUDMethods which you can instantiate. (Search CP for plugin based architectures if you aren't aware of how to make it work; you should just need the simple, one AppDomain version here as you don't need to unload or version-control the plugins.) That way, you only have one slow piece of late binding (essentially, binding the type to the right assembly), and everything after that can go through the interface (which should be declared in an assembly that the application and both plugins have access to do, either the application or a fourth separate DLL, depending on whether these classes are application dependent).