高级会员
注册日期: 06-11
帖子: 14579
精华: 1
现金: 224494 标准币
资产: 234494 标准币
|
【转帖】dwgdirect 2.6.3 registry problem - class not registered
dwgdirect 2.6.3 registry problem - class not registered.
dwgdirect 2.6.3 registry problem - class not registered.
i have upgraded to dwgdirect2.6.3. it is given in the release notes that there is not need to register these new dlls. i could build my project perfectly.
but my software is failing to open the .dxf/.dwg files. through debugger i came to know that its failing to instantiate the dxffileloader object and the corresponding error is "class not registered".
can any one please suggest me how to fix this problem?
thanks in advance.
bala.
what is the call stack at the exception point?
can our samples, such as odamfcapp open the same file?
vladimir
yes odamfcapp open the same file.
the problem is there is no need to register the dwgdirect 2.6.3 dlls.
even in my project im not registing the dlls. when i try to access the object it fail with the "class not registered" message. should any thing be done to manifest file? or anything else?
thanks
bala.
try to build debug version, and see what is the call stack when the exception happens.
vladimir
i have tried to catch the exception. its not throwing any exception.
instead its crashing with runtime error r6034 when im trying to register the class id
if ( succeeded( loader.cocreateinstance( rgclsid[ i ] ) ) )
when i try to do this its failing with run time error r6034.
ccomptr< idxffileloader > dxffileloader;
ccomptr< idwgfileloader > dwgfileloader;
if ( !succeeded( hr = dxffileloader.cocreateinstance( __uuidof( idxffileloader ) ) ) )
{
::messagebox( null, "failed to create dxffileloader collection", "!", mb_ok );
}
the value in the hr is "class not registered".
i have attached the screen shot of the runtime error.
dwgdirect 2.6.3 dlls should not be registered. so, what else should be done to get the things work.
is the manifest file another way of registering the components and to get the things work? how?
attached images (16.0 kb, 2 views)
probably adding manifest to the application may indeed help you,
see this thread for manifest example:
vladimir
thank you .
my problem has been solved by adding a manifest file.
|