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 have a native c++ app, and I want to use some managed types that are in a separate managed dll. I believe that one way to do this and still keep the c++ app totally native is to use COM interop with .NET. However my problem is that my app has to initially run on machines that don’t have the CLR installed, so I don’t want the CLR to be loaded unless I actually make use of the codepath that calls into the managed DLL.
How can I delay load the managed DLL?
I think the best way to achieve this is via COM interop, native to managed in this case. If you’re app is native it wont’t load the CLR by default. You can “delay load” the CLR by creating a COM object which is defined in the managed assembly only when it’s actually required. The COM layer of the CLR will take care of loading the CLR at that point and returning a CCW to the managed object.