Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am currently using a static delegate in a wrapper class for a C dll to avoid that the delegate, which points to a unsafe function, gets garbaged collected.
This was working fine until I have now the requirement to support multiple instances of the class. A workaround might be to keep a list of the static delegates, but I would like to find a simpler solution.
To keep an object from being collected, you must maintain a reference to it.
Static members in static classes live for application lifetime.
For instance class members, depending on your class design and project design, you may take different approaches. Maintaining a static list may not be a bad idea.
My only question is how are you able to figure that the delegate is being collected. Because, if you are able to access it, then you must have maintained a reference of it. In which case, it must have stayed in memory.