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.
1) .NET Assembly MyAssembly.dll implements a Singleton class MyClass
2) A .NET APP has a reference to MyAssembly.dll and uses MyClass
3) A .NET ActiveX MyActiveX.dll implements a COM Visible class wich in turn references to MyClass in MyAssembly.dll
My question is: if the app and the ActiveX are running at the same time (the ActiveX in a web page), do I have one or two instances of MyAssembly.dll loaded? I need it to be one instance for the singleton to work.
Thanks
The assembly is loaded into the Application Domain, static fields (where the singleton is based on) are instantiated per Application Domain. There is at least one App Domain per process, so you get at least one instance per process.
Your ActiveX component is instantiated in another process then the .NET Application. You don’t get shared memory.
To instantiate the singleton only once, you need to start a single process and access it remotely. You could achieve this by the use of remoting, DCOM, WCF or something like this. You need to make sure that both process access the this instance.