VC ATL, Suddenly can't register ATL COM class

Suddenly can't register ATL COM class

Author	Message
morell #1 / 5	Suddenly can't register ATL COM class I wondered if anyone has met a problem like this before. Is there anything worth checking quickly... I've been developing an ATL COM object, testing as I go using a simple VB application. As I add new methods I rebuild the ATL, add another test button to the VB app, and everything works fine. Until now. For no apparent reason, the VB app throws up saying that the object cannot be created because it isn't registered. I knocked up a quick delphi test prog and got the same problem. I've tried the obvious things, ie deleting every trace of the COM object from the registry then rebuilding it from scratch, also removing the ref from VB and adding it back again, but still the same error. Any ideas? The brute force solution I suppose is to "start again" with a fresh ATL object, and port my code back into it. Anything I could try before I go down that route? TIA Tom -- Morello Publishing Ltd http://www.--*.com/ Manage your passwords with Morello KeyRing
Tue, 09 Dec 2003 05:42:48 GMT

Parallel #2 / 5	Suddenly can't register ATL COM class try registering it via regsvr32 (as opposed to the build). if it doesn't work, regsvr puts up a message box with the error code (HRESULT) which may help in determining the problem.. Quote: > I wondered if anyone has met a problem like this before. Is there anything > worth checking quickly... > I've been developing an ATL COM object, testing as I go using a simple VB > application. As I add new methods I rebuild the ATL, add another test button > to the VB app, and everything works fine. > Until now. For no apparent reason, the VB app throws up saying that the > object cannot be created because it isn't registered. I knocked up a quick > Delphi test prog and got the same problem. > I've tried the obvious things, ie deleting every trace of the COM object > from the registry then rebuilding it from scratch, also removing the ref > from VB and adding it back again, but still the same error. > Any ideas? The brute force solution I suppose is to "start again" with a > fresh ATL object, and port my code back into it. Anything I could try before > I go down that route? > TIA > Tom > -- > Morello Publishing Ltd > http://www.morello.co.uk > Manage your passwords with Morello KeyRing
Tue, 09 Dec 2003 14:15:40 GMT

morell #3 / 5	Suddenly can't register ATL COM class Quote: > try registering it via regsvr32 (as opposed to the build). if it doesn't > work, regsvr puts up a message box with the error code (HRESULT) which may > help in determining the problem.. Thanks, but I already tried that. It appears to register, and unregister, without error - but it still doesn't work with VB or Delphi. It worked for ages until now. Perhaps I should try with a VC client. VB and, I think, Delphi, use the disp interface. Not that it will solve the problem, I need it to work with everything. Tom -- Morello Publishing Ltd http://www.morello.co.uk Manage your passwords with Morello KeyRing
Tue, 09 Dec 2003 14:48:18 GMT

Christian McArdl #4 / 5	Suddenly can't register ATL COM class Quote: > Thanks, but I already tried that. It appears to register, and unregister, > without error - but it still doesn't work with VB or Delphi. It worked for > ages until now. Is the type library being correctly generated and registered? Christian.
Tue, 09 Dec 2003 18:08:26 GMT

Dmitry Guli #5 / 5	Suddenly can't register ATL COM class Compare UIDs in idl and rgs files? Do they match? I had same problem with outdated rgs information. Set VB as a host application for debug session, put a bunch of breakpoints and try to find out if the object's class factory, constructor, FinalConstruct, etc is called? Maybe something wrong in there, dunno? Regards. Quote: > I wondered if anyone has met a problem like this before. Is there anything > worth checking quickly... > I've been developing an ATL COM object, testing as I go using a simple VB > application. As I add new methods I rebuild the ATL, add another test button > to the VB app, and everything works fine. > Until now. For no apparent reason, the VB app throws up saying that the > object cannot be created because it isn't registered. I knocked up a quick > Delphi test prog and got the same problem. > I've tried the obvious things, ie deleting every trace of the COM object > from the registry then rebuilding it from scratch, also removing the ref > from VB and adding it back again, but still the same error. > Any ideas? The brute force solution I suppose is to "start again" with a > fresh ATL object, and port my code back into it. Anything I could try before > I go down that route? > TIA > Tom > -- > Morello Publishing Ltd > http://www.morello.co.uk > Manage your passwords with Morello KeyRing
Tue, 09 Dec 2003 20:39:53 GMT

Page 1 of 1

[ 5 post ]