Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Native WiFi programming API
738 views
Skip to first unread message
David Harmon
Feb 12, 2013, 10:23:23 PM2/12/13
to
I am trying to write a C++ program using the Native WiFi API as
described at
http://msdn.microsoft.com/en-us/library/windows/desktop/ms706274%28v=vs.85%29.aspx
I installed Visual Studio 2012 Express, and I am using the wlanapi.h
header that came with it and linking with the wlanapi.lib likewise.
Compile and link goes fine but when I try to run it on Windows 7 I
get a message box displayed with the message
"The procedure entry point WFDCloseHandle could not be
located in the dynamic link library wlanapi.dll."
The wlanapi.dll apparently came as part of windows 7. I can post
example code, but I do not think it is a problem in my code as the
same thing happens whether or not I include the call to
WFDCloseHandle. I can't believe that basic fundamental entry point
has been eliminated. So, what gives? How can I fix this?
described at
http://msdn.microsoft.com/en-us/library/windows/desktop/ms706274%28v=vs.85%29.aspx
I installed Visual Studio 2012 Express, and I am using the wlanapi.h
header that came with it and linking with the wlanapi.lib likewise.
Compile and link goes fine but when I try to run it on Windows 7 I
get a message box displayed with the message
"The procedure entry point WFDCloseHandle could not be
located in the dynamic link library wlanapi.dll."
The wlanapi.dll apparently came as part of windows 7. I can post
example code, but I do not think it is a problem in my code as the
same thing happens whether or not I include the call to
WFDCloseHandle. I can't believe that basic fundamental entry point
has been eliminated. So, what gives? How can I fix this?
Geoff
Feb 13, 2013, 12:54:36 AM2/13/13
to
http://msdn.microsoft.com/en-us/library/windows/desktop/hh448246(v=vs.85).aspx
States that it pertains to the WiFi Direct feature of "Windows 8" minimum client
and minimum supported server is Windows Server 2012. This would appear to mean
that any OS of Windows 7 or earlier is not supported.
Inspecting the wlanapi.dll with Dependency Walker shows no WFD* functions
exported at all, only Wlan* functions. My DLL on Windows 7 Pro 64-bit is
6.1.7600.16385.
I'm surprised you didn't get a warning about a failure to find WFDOpenHandle.
David Harmon
Feb 13, 2013, 11:27:22 AM2/13/13
to
On Tue, 12 Feb 2013 21:54:36 -0800 in
comp.os.ms-windows.programmer.win32, Geoff <ge...@invalid.invalid>
wrote,
comp.os.ms-windows.programmer.win32, Geoff <ge...@invalid.invalid>
wrote,
>The article:
>http://msdn.microsoft.com/en-us/library/windows/desktop/hh448246(v=vs.85).aspx
>
>States that it pertains to the WiFi Direct feature of "Windows 8" minimum client
>and minimum supported server is Windows Server 2012. This would appear to mean
>that any OS of Windows 7 or earlier is not supported.
>
>Inspecting the wlanapi.dll with Dependency Walker shows no WFD* functions
>exported at all, only Wlan* functions. My DLL on Windows 7 Pro 64-bit is
>6.1.7600.16385.
>
>I'm surprised you didn't get a warning about a failure to find WFDOpenHandle.
Doh! I should be calling WlanOpenHandle. Thank you very much.
>http://msdn.microsoft.com/en-us/library/windows/desktop/hh448246(v=vs.85).aspx
>
>States that it pertains to the WiFi Direct feature of "Windows 8" minimum client
>and minimum supported server is Windows Server 2012. This would appear to mean
>that any OS of Windows 7 or earlier is not supported.
>
>Inspecting the wlanapi.dll with Dependency Walker shows no WFD* functions
>exported at all, only Wlan* functions. My DLL on Windows 7 Pro 64-bit is
>6.1.7600.16385.
>
>I'm surprised you didn't get a warning about a failure to find WFDOpenHandle.
0 new messages