Dispose a imported DLL

Question

0.00/5 (No votes)

See more:

In my code im importing a DLL using DllImport("OTVPlayer.dll")] and using its methods. How can I dispose this DLL after using? Please help. very urgent

Posted 11-Jan-12 22:20pm

Member 8089914

Updated 12-Jan-12 2:57am

Mehdi Gholam

v2

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)

Catalin Serafimescu · Answer 1 · 2012-01-11T23:28:00

Solution 1

In .NET you cannot unload modules/assemblies unless you unload all AppDomain. The unamanaged libraries should be released when calling assembly is unloaded.

Try to create a new AppDomain, do your stuff and when you finish, unload it. It's not nice, I know.

Posted 11-Jan-12 23:28pm

Catalin Serafimescu

Comments

Member 8089914 12-Jan-12 9:44am

Can you give me more details ? a reference also be fine

Catalin Serafimescu 12-Jan-12 9:48am

http://stackoverflow.com/questions/97433/good-example-of-use-of-appdomain
http://msdn.microsoft.com/en-us/library/system.appdomain.aspx <-- lots of samples

http://blogs.msdn.com/b/cbrumme/archive/2003/06/01/51466.aspx

Andreas Gieriet 12-Jan-12 14:42pm

Hi Catalin Serafimescu,
why "not nice"? It's problably the only way to do it.
Cheers
Andi

Catalin Serafimescu 12-Jan-12 16:17pm

The objects needs to be marshaled. And you can't do that with any objects. And, compared with 'regular' programming, it's more complicated.
Also, from the name of the DLL I suspect this is some player. Not sure, but I think streaming is impossible between domains. In any case, I wonder why unload the player DLL...

Member 8089914 13-Jan-12 0:08am

thank for everything. Actually to clarify you more this is a DLL intergrated with a player. Im passing the parameters to the DLL and the DLL shows the corresponding video stream in the player.but I can see DLL is still have a reference to my application although I close the related windows form. I dont want this and I want to release the DLL. this is the problem Im having.

Catalin Serafimescu 13-Jan-12 2:34am

"Premature optimization is the root of all evil".
I think you want to say 'my application has a reference to DLL'. I think you open the player in a child form and want to release the libs when you close it. Loading and unloading libraries is time-consuming. I think you should not do this unless you have a very strong reason.
There might be another way, but I'm not too sure and introduces another layer: if your DLL is native (unmanaged), you could write a managed C++ wrapper over it and you load it dynamically, then you release it. It might work.