complib.hlp

complib.hlp

• ndarwish

  What do you have on SqlManager.cpp line 1

  Thanks,

  Ayman Shoukry

  VC++ Team

  
  
  

• WizDum

  I found a workaround that allows precompiled headers to work as well... if you set the project options to "Use Precompiled Headers", then right-click the stdafx.cpp file and set the precompiled headers option to "Create Precompiled Headers" just for that file, then the entire project builds and you get the improved speed from using the precompiled headers. At least this worked for me...
  
  -Joe
  
  

• Mike Haladjian

  #include "StdAfx.h"

  
  

• BringerOD

  I am having a similar problem with files I added to a new project. On my system, turning off precompiled headers would allow the project to build. Strangely, though, if I try to re-create the precompiled headers with the /Yc option, it builds fine, but then when I try to use the precompiled headers with the /Yu option, I start getting that error message about the complib.hlp file again.

  
  

• Erik Edlund

  I saw that source file while looking complib.hlp on the web too. I didn't think this had anything to do with though.

  I've never installed Rotor or even knew about it. The only visual studio product I have installed in this computer is visual c++ 2005 express so I can't think of where I got this file from. Also another thing is that the problem only happens when I move a project from one computer to another and try work from the project file.

  Also this is a brand new project so there is no old code in it.

  I really can't think of why this is happening.

  
  

• kath

  Could you paste such files here just in case Without being able to reproduce the issue, it is really hard to speculate what might be happening.

  Thanks,

  Ayman Shoukry

  VC++ Team

  
  
  

• genyded

  I just created a new project with some code in it. If I remember correctly it was only a console project. It had clr enabled.

  I used the visual c++ wizzard for new projects. The problem comes when you move the project with all its files and try to re-compile it.

  Also pre-compiled headers were enabled by default which is what was causing the problem. As soon as I removed pre-compiled headers support it worked just fine.

  Alan.

  
  

• narendrakg

  This looks similar to http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=269105&SiteID=1.

  Could you post a sample source code reproducing it

  Thanks,

  Ayman Shoukry

  VC++ Team

  
  
  

• Srini Kuchi

  This doesn't really make much since as other files include this file but if I remove these two files SqlUser.cpp and SqlManager.cpp it compiles and links fine.

  Also all there is in those files are empty definitions for the constructor and destructor of the class.

  I cannot recreate the the problem by just creating a project with the same files.

  
  

• Dania151638

  Alan, you mentioned that "I just started working on the project today so there really isn't anything in the code itself that would cause anything like this IMO.". Can you please let us know what kind of project you were creating and the steps you used to create the project Can you reproduce the problem with the project created by VS2005 without adding any of your own code

  Thanks,

  Ann Zhou

  Visual C++

  
  
  

• Very Anonymous

  May the help folks know more about the complib.hlp file

  Thanks,

  Ayman Shoukry

  VC++ Team

  
  
  

• Paul Ballard

  Hi Alan - have you tried searching for complib.hlp on the machine where the code works to see where it is installed That may give a clue as to what's going on.

  Also, I noticed that the sample code had no path to the .hlp file specified. This code would only work then if the .hlp file were able to be found either on the path or via an entry in the registry. The area to look for the file in the registry would be here:

  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Help

  
  
  

• FreddyFresh

  Well, this is strange and rather obscure. I can only speculate as to what is going on. I've poked around for a short while and can find no record of a standard Help file named complib.hlp.

  First of all, code calling Help in ".hlp" format is likely to be code that is several years old. The Microsoft ".hlp" Help-file format was succeeded by the ".chm" Help-file format years ago; I can't recall how many.

  I searched the Web for "complib.hlp" and found very few results. The one where code is used is here: http://dotnet.di.unipi.it/Content/sscli/docs/doxygen/clr/clr/posterror_8cpp-source.html

  That page was published in July 2002 and appears to be from a beta doc set called "Rotor CLR Documentation." (You can read about the thing called "Rotor" here: http://research.microsoft.com/Collaboration/University/Europe/RFP/Rotor/. I think Rotor did not get much past the stage described.)

  The posterr_8cpp_source.html page begins with a call to stdafx.h, which is a common precompiled header file, right Here's a snippet from posterr.cpp:

  00578 //*****************************************************************************
  00579 // Create, fill out and set an error info object. Note that this does not fill
  00580 // out the IID for the error object; that is done elsewhere.
  00581 //*****************************************************************************
  00582 HRESULT FillErrorInfo( // Return status.
  00583 LPCWSTR szMsg, // Error message.
  00584 DWORD dwHelpContext) // Help context.
  00585 {
  00586 ICreateErrorInfo *pICreateErr; // Error info creation Iface pointer.
  00587 IErrorInfo *pIErrInfo = NULL; // The IErrorInfo interface.
  00588 HRESULT hr; // Return status.
  00589
  00590 // Get the ICreateErrorInfo pointer.
  00591 if (FAILED(hr = CreateErrorInfo(&pICreateErr)))
  00592 return (hr);
  00593
  00594 // Set message text description.
  00595 if (FAILED(hr = pICreateErr->SetDescription((LPWSTR) szMsg)))
  00596 goto Exit1;
  00597
  00598 // Set the help file and help context.
  00599 if (FAILED(hr = pICreateErr->SetHelpFile(L"complib.hlp")) ||
  00600 FAILED(hr = pICreateErr->SetHelpContext(dwHelpContext)))
  00601 goto Exit1;

  
  I'm not a C++ programmer, so I can't grasp how this foul-up might have come about, but I image that one of your systems has a file like this on it. Maybe you have Rotor source code on your computer. And you probably have multiple stdafx.h files on your system as well. Perhaps the wrong one, an out-of-date version of stdafx.h, is getting pulled into your compilation somehow, and pointing to code like that above.

  
  
  

• Redhaze

  So I recreated the project with the old source files and it worked fine. now I brought the modified files back to my home desktop and the same thing is happening now with other files.

  For some reason c++ appears to be trying to access the file complib.hlp which I have no clue what it's for nor is it in either of my computers.

  There isn't anything out of the normal in the source files. These files are pretty much simple classes. I just started working on the project today so there really isn't anything in the code itself that would cause anything like this IMO.

  
  
• complib.hlp