I noticed that the attempt to test comcat.dll on Win98 failed because DllRegisterServer is a stub returning E_NOTIMPL. I have added the registry entries for the component categories manager to winedefault.reg, which should suffice for normal Wine installations. Despite this, is it generally acceptable to have actual code to register/unregister a standard COM server DLL in its Dll[Un]RegisterServer? It would be redundant for normal Wine, but hey, it's not big or complex.
Despite this, is it generally acceptable to have actual code to register/unregister a standard COM server DLL in its Dll[Un]RegisterServer? It would be redundant for normal Wine, but hey, it's not big or complex.
If you could implement this it would rock as I need it for the Mingw port and Patrik will need it for his VC++ port.
__________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com
"John K. Hohm" jhohm@acm.org writes:
I noticed that the attempt to test comcat.dll on Win98 failed because DllRegisterServer is a stub returning E_NOTIMPL. I have added the registry entries for the component categories manager to winedefault.reg, which should suffice for normal Wine installations. Despite this, is it generally acceptable to have actual code to register/unregister a standard COM server DLL in its Dll[Un]RegisterServer? It would be redundant for normal Wine, but hey, it's not big or complex.
Actually putting that in DllRegisterServer is arguably the right way to do it. What we should have is some kind of installation step that would register the Wine dlls, instead of having to put everything in winedefault.reg.
Alexandre Julliard wrote:
"John K. Hohm" jhohm@acm.org writes:
I noticed that the attempt to test comcat.dll on Win98 failed because DllRegisterServer is a stub returning E_NOTIMPL. I have added the registry entries for the component categories manager to winedefault.reg, which should suffice for normal Wine installations. Despite this, is it generally acceptable to have actual code to register/unregister a standard COM server DLL in its Dll[Un]RegisterServer? It would be redundant for normal Wine, but hey, it's not big or complex.
Actually putting that in DllRegisterServer is arguably the right way to do it. What we should have is some kind of installation step that would register the Wine dlls, instead of having to put everything in winedefault.reg.
Would it be a good idea to create a bug report for this?... Or does someone want to implement it right away...
Tony Lambregts
Quoting Tony Lambregts tony_lambregts@telusplanet.net:
which should suffice for normal Wine installations. Despite this, is it generally acceptable to have actual code to register/unregister a
standard
COM server DLL in its Dll[Un]RegisterServer? It would be redundant for normal Wine, but hey, it's not big or complex.
Actually putting that in DllRegisterServer is arguably the right way to do it. What we should have is some kind of installation step that would register the Wine dlls, instead of having to put everything in winedefault.reg.
Would it be a good idea to create a bug report for this?... Or does someone want to implement it right away...
I was just about ready to send the last patch to complete the comcat.dll implementation, fixing bug 652. I don't think another bug is necessary; I'll implement Dll[Un]RegisterServer before pronouncing the bug fixed. Hopefully doing this in the next couple of days will be "right away" enough for you. ;-)
John K. Hohm wrote:
I was just about ready to send the last patch to complete the comcat.dll implementation, fixing bug 652. I don't think another bug is necessary; I'll implement Dll[Un]RegisterServer before pronouncing the bug fixed. Hopefully doing this in the next couple of days will be "right away" enough for you. ;-)
Plenty fast enough.
Tony Lambregts
-
Alexandre Julliard -
John K. Hohm -
Steven Edwards -
Tony Lambregts