This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(118.4, 76%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EH%3C/text%3E%3C/svg%3E)
We have been using the Mobile Broadband API (MBN API) for our development. According to the information we obtained from the Microsoft website, it will be gradually replaced by the Windows Runtime API. In that case, how should we handle MBN-related events in native environments such as Windows Native Service, MFC projects, and normal console apps?
eg:
https://learn.microsoft.com/en-us/windows/win32/api/mbnapi/nn-mbnapi-imbnconnection
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 34%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EXY%3C/text%3E%3C/svg%3E)
Hello @Hunter,
It doesn't mean the Mobile Broadband API (MBN API) will be removed. It's recommended to use the Windows.Networking.Connectivity namespace.
To use the Windows.Networking.Connectivity namespace in native environments, see Get started with C++/WinRT for more information.
Hello Yang:
Broadband API will continue support in Windows 11 and future Windows ? right ?
Actually, we have a native program with drivers to complete some spec operation. these will submit to Windows update. now it is currently unclear whether there are any unknown issues when migrating to UWP.
Hello Yang:
Broadband API will continue support in Windows 11 and future Windows ? right ?
Actually, we have a native program with drivers to complete some spec operation. these will submit to Windows update. now it is currently unclear whether there are any unknown issues when migrating to UWP.
@Hunter, I noticed that the Mobile Broadband API is not marked as deprecated like for example mmioOpen but It's preferred to use the Windows.Networking.Connectivity namespace.
The Windows.Networking.Connectivity namespace, C++/WinRT API, is usable not only in UWP but also in other applications. @Hunter, any update?
Yes, not only in UWP but also in other applications. I have tried using MobileBroadbandAccountWather in a UWP application and normal console application. But in normal console application did not received any delegate call , UWP can.
The API has a special specification.
Note This functionality is available only to mobile operator apps and UWP apps given privileged access by mobile network operators. If you want to use this API and publish your app to the Microsoft Store, then you'll need special approval. For more information, see the Restricted capabilities section in the App capability declarations topic.
It's simplest to use it in UWP.
Yes，ware are considering migrating to a UWP project. Thank you for your response.