Re: VC++ .NET> Release Build results LNK2001, LNK2019 and LNK1120

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Oleg Starodumov (com-dot-debuginfo-at-oleg)
Date: 02/28/05


Date: Mon, 28 Feb 2005 12:44:11 +0200


> I have written /verbose::lib into that place before your answer.
> Unfortunately, it still gives the LNK2001 error for all WinSock functions,
> when I build in Release Mode.
>

/verbose option does not affect the outcome of linking, it only provides
some troubleshooting output in build output window.
Please look at that window and see whether the linker was able to find ws2_32.lib.
Also compare the output with debug build, to see if there are differences.

Regards,
Oleg



Relevant Pages

  • Re: VC++ .NET> Release Build results LNK2001, LNK2019 and LNK1120
    ... > Unfortunately, it still gives the LNK2001 error for all WinSock functions, ... some troubleshooting output in build output window. ... Also compare the output with debug build, to see if there are differences. ... Regards, ...
    (microsoft.public.dotnet.general)
  • Re: VC++ .NET> Release Build results LNK2001, LNK2019 and LNK1120
    ... > Unfortunately, it still gives the LNK2001 error for all WinSock functions, ... some troubleshooting output in build output window. ... Also compare the output with debug build, to see if there are differences. ... Regards, ...
    (microsoft.public.vc.debugger)
  • Debug help please...
    ... I have just discovered a bug in my application. ... the debug version, so the release version is fine. ... The output window is pretty long, so I have included it at the end of this ... Binary was not built with debug information. ...
    (microsoft.public.vc.mfc)
  • Re: Debug help please...
    ... The release version is also broken, but unlike the debug version, IT DOES ... So you find and fix the bug. ... The output window is pretty long, so I have included it at the end of this ... Binary was not built with debug information. ...
    (microsoft.public.vc.mfc)
  • starting app to debug in VS2003.net takes "forever"
    ... anymore to debug them. ... The VS2003.net output window says: ... security updates, and there is no way to uninstall them. ...
    (microsoft.public.vsnet.debugging)