Re: self-register problem (linker bug?)

What version of the OS are you using? Are you logged in as administrator? Is the
message actually correct [Do you have rights to modify the Registry]?
joe

On Wed, 7 Feb 2007 15:32:39 +0100, "Eric" <bauersachs@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:

When I create my DLL then I get the following error message:
1>Linking...
1> Creating library D:\Project\xxxx\Release Unicode\PROJ.lib and object
D:\Project\xxxx\Release Unicode\PROJ.exp
1>Embedding manifest...
1>Registering output...
1>Project : error PRJ0050: Failed to register output. Please ensure you have
the appropriate permissions to modify the registry.
1>Build log was saved at "file://d:\Project\xxxx\Release
Unicode\BuildLog.htm"
1>PROJ - 1 error(s), 0 warning(s)

Trying to register it by myself with regsvr32 results in:
DllRegisterServer in proj.dll failed.
Return code was: 0x80029c4a
(This means "Error Loading Type Library")

To fix this problem I found out that I had to include the type library into
the DLL. Some older article, written by Igor Tandetnik, says that in the
resource file I should include the TLB:
1 TYPELIB "ProjectName.tlb"
To check if it worked you can use the OLE/COM Object Viewer and select View
TypeLib and select the DLL.
I made this include by setting the option "Linker / Embedded IDL / Type
Library" to $(ProjectDir)$(IntDir)\PROJ.tlb instead of modifying the
resource file.

This works. But now I have the problem that I have the same error message in
the release configuration and the above mentioned change isn't enough. I
found out that to get it work there I had to enable incremental linking.
What has incremental linking to do with including a type library? Is this a
linker bug? I'm using Visual Studio C++ 2005 SP1.

Eric

Joseph M. Newcomer [MVP]
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
.

Relevant Pages

  • Re: sus office updates
    ... You can modify the registry ... or you can script a change for MSI to add ... my "encrypted" product code for Office 2003 Professional is: ...
    (microsoft.public.sms.tools)
  • Re: Virtual Memory
    ... You'd be better off modifying the registry through the ... optimize you swap file settings. ... >> is receiving virtual memory errors with the pagefile. ... There was not an article for 2000 to modify ...
    (microsoft.public.win2000.registry)
  • Re: script error message in Outlook Express 6
    ... I read the page links you gave me and found the spots to modify in my ... registry. ... You need to turn on scripting in the security settings for the ... >> for a particular Zone. ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • Re: Process User Rights
    ... > reasons the Registry is protected. ... > It is naive to assume that you have the right to modify the Registry. ... In a well-designed security system (which ... > protection we have now, and I see no reason to try to defeat that. ...
    (microsoft.public.vc.mfc)
  • Re: self-register problem (linker bug?)
    ... I have the right to modify the registry. ... the problem only occurs when incremental linking is ... message actually correct [Do you have rights to modify the Registry]? ...
    (microsoft.public.vc.mfc)
Loading