I included this header <winsock2.h>, my code did not compile eventhough i have not wrote any code relates to winsock yet.
I followed this instructions: http://www.errorbase.net/
I added this in additional dependencies: "C:\Program Files\Microsoft SDKs\Windows\v6.0A\Lib\WS2
I still get same errors as before. Can you tell me how to fix this problem?
NOTE: i followed the steps, which is mentioned in the link above, in VC++ Express & it worked. But that was several months ago. Now i have VS Studio 2008
Extra Q: what is ws2def.h for?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
>>>>> I never expected the order of headers is kind of important.
Normally it shouldn't. Each piece of source, header or implementation should include the headers needed and only these.
But of course if the header b.h needs some definitions made in a.h the b.h has to include a.h and not the other way round.
In case of a enhancement, developers - even members of the major and leading companies - sometimes have funny ideas. They supply a new header which was supposed to replace an older one but they don't change the older header for compatibility reasons. And sometimes - as it was with winsock.h - the older header survived as the enhancements coming with winsock2.h were only important for a few projects. Moreover, the non-Windows community ignored the winsock2.h hence it was a MS proprietary solution.
>>>> so does this mean will take winsock2.h as the main winsock header & ignore the old version?
Yes, the winsock2.h defines the macro which causes a further include of winsock.h to skip all the definitions and includes made in winsock.h. But if you have a file which includes winsock.h prior to winsock2.h you'll get the problems you posted above. It might be 10 or more years ago when I had the same problems.
>>>> Which one is better, #include<Ws2tcpip.h> & #include<Winerror.h>
I never included the first one and often used the second one - less to actually make an own error handling but to simply find out what a specific error returned by GetLastError means. There are runtime functions which would translate a given error code to the text given in winerror.h. I never used them myself cause a look to winerror.h does the same and I never had a reason to automate that.
>>>> i just do this: #include<windows.h>?
>>>> Why this is better?
I don't know whether it is *better* but you could trust when including windows.h that all basic WINAPI was included. The questions arise if you want to use more than the basics. Do you have to include the additional headers before or after windows.h. As a rule of thumb, I would include them before cause they often include windows.h theirselfes at the right order, so your own include of windows.h was skipped and it was good so cause windows.h needed to be included in order. Some headers really were independent and you can include them before or after, it doesn't matter.
Business Accounts
Answer for Membership
by: itsmeandnobodyelsePosted on 2009-01-25 at 00:42:44ID: 23460103
The problem is that both winsock.h and winsock2.h were included which have most definitions in common. winsock2.h knows of winsock.h but not the other way rounde. Hence, you need to include winsock2.h *before* winsock.h. If using stdafx.h you should try to include winsock2.h as early as it compiles. If not, try to include winsock2.h as the very first include in each cpp. If this doesn't help or give other errors, open the winsock.h and check which macro protects from including it twice.. It should be like
#ifdef _winsock_h_included_
#define _winsock_h_included_
if found define the _winsock_h_included_ as a preprocessor macro in your project setting (simply add it to the other macros like _WIN32)