Sign in
Tripp Parks's WebLog
Translate This Page
Translate this page
Powered by
Microsoft® Translator
Options
Blog Home
Share this
RSS for posts
Atom
RSS for comments
Search
Tags
Data usage
Networking - General
Networking - P2P
Windows 8
Archive
Archives
December 2012
(2)
July 2012
(12)
June 2012
(3)
September 2007
(1)
July 2007
(3)
June 2007
(10)
May 2007
(1)
October 2006
(2)
September 2006
(12)
July 2006
(5)
June 2006
(6)
May 2006
(2)
April 2006
(5)
March 2006
(6)
February 2006
(7)
January 2006
(6)
December 2005
(8)
November 2005
(1)
October 2005
(14)
September 2005
(5)
August 2005
(17)
July 2005
(14)
June 2005
(8)
May 2005
(1)
January 2005
(1)
December 2004
(1)
November 2004
(1)
E_INVALID_ARRRRRRRRRRRGH
MSDN Blogs
>
Tripp Parks's WebLog
>
E_INVALID_ARRRRRRRRRRRGH
E_INVALID_ARRRRRRRRRRRGH
tparks
5 Oct 2005 1:31 AM
Comments
0
What's the most annoying api you've ever used?
Mine pretty much has to be the winsock NSP as it is probably the hardest api in Windows to use
behind the relatively harmless looking
INT WSALookupServiceBegin(
LPWSAQUERYSET
pQuerySet
,
DWORD
dwFlags
,
LPHANDLE
lphLookup
);
lay 10 pointers of PAIN! (in the first level alone!)
typedef struct _WSAQuerySet {
DWORD
dwSize
;
LPTSTR
lpszServiceInstanceName
;
LPGUID
lpServiceClassId
;
LPWSAVERSION
lpVersion
;
LPTSTR
lpszComment
;
DWORD
dwNameSpace
;
LPGUID
lpNSProviderId
;
LPTSTR
lpszContext
;
DWORD
dwNumberOfProtocols
;
LPAFPROTOCOLS
lpafpProtocols
;
LPTSTR
lpszQueryString
;
DWORD
dwNumberOfCsAddrs
;
LPCSADDR_INFO
lpcsaBuffer
;
DWORD
dwOutputFlags
;
LPBLOB
lpBlob
;
} WSAQUERYSET,
Needless to say its pretty difficult to use (and even harder to get to work with C#) but it does try to cover a lot of different types of name resolution and other network events (Bluetooth,PNRP,NLA,DNS,SAP,WINS,X500,NETBT). But that doesn’t make it anymore fun to use:)
What's your nightmare?
0 Comments
Blog - Comment List MSDN TechNet
Comments
Loading...