I found an out-proc COM server implemented (supposedly due to a bug) in such way that if a client calls CoGetClassObject() and then never tries to instantiate anything with the retrieved factory the s
Iam getting the following linker error while building an atl com dll which is targeted to IA64 using a makefile on an XP platform..
IFileDialog *pfd; ... CoCreateInstance(CLSID_FileOpenDialog,NULL, CLSCTX_INPROC_SERVER,IID_PPV_ARGS(&pfd));
Retrieving the COM class factory for component with CLSID {AD37B7D5-B5A3-460A-8FFB-3C71984A4537} failed due to the following error: 80040154.
开发者_JAVA百科 It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical andcannot be reasonably answered in its current form.
I have created a new simple COM object in Visual Studio 2008 using the ATL-wizard. The object has a single class and simple methods. The ATL-wizard did generate .rgs-files for my class.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
MSDN says CoRevokeClassObject() informs COM that some COM class is no longer available for instantiation.
I have two COM objects written in C++ and ATL. There are in one library and I know their IIDs and CLIDs.
I am using MFC in my C++ program (using Visual Studio 2008). I have to call AfxGetInstanceHandle() at the begining of my program.