RFCOMM Scenario: Receive File as a Server
Language: HTML | XAML

RFCOMM Scenario: Receive File as a Server(XAML)

[This article is for Windows 8.x and Windows Phone 8.x developers writing Windows Runtime apps. If you’re developing for Windows 10, see the latest documentation]

Another common RFCOMM App scenario is to host a service on the PC and expose it for other devices. In this scenario, the App developer first creates a RfcommServiceProvider to advertise the desired service. The developer then sets the SDP attributes as needed (using established data helpers to generate the attribute’s Data) and starts advertising the SDP records for other devices to retrieve. To connect to a client device, the App developer creates a socket listener to start listening for incoming connection requests. When a connection is received, the developer can store the connected socket for later processing. When it’s time to receive the file, the App developer can follow established data stream patterns to read chunks of data from the socket’s InputStream and save it to a file.

Windows.Devices.Bluetooth.RfcommServiceProvider _provider;

async void Initialize()
    // Initialize the provider for the hosted RFCOMM service
    _provider = await Windows.Devices.Bluetooth.

    // Create a listener for this service and start listening
    StreamSocketListener listener = new StreamSocketListener();
    listener.ConnectionReceived += OnConnectionReceived;
    await listener.BindServiceNameAsync(

    // Set the SDP attributes and start advertising

const uint SERVICE_VERSION = 200;
void InitializeServiceSdpAttributes(RfcommServiceProvider provider)
    auto writer = new Windows.Storage.Streams.DataWriter();

    // First write the attribute type
    // Then write the data
    auto data = writer.DetachBuffer();
    provider.SdpRawAttributes.Add(SERVICE_VERSION_ATTRIBUTE_ID, data);

void OnConnectionReceived(
    StreamSocketListener listener,
    StreamSocketListenerConnectionReceivedEventArgs args)
    // Stop advertising/listening so that we’re only serving one client
    await listener.Close();
    _socket = args.Socket;

    // The client socket is connected. At this point the App can wait for
    // the user to take some action, e.g. click a button to receive a file
    // from the device, which could invoke the Picker and then save the
    // received file to the picked location. The transfer itself would use
    // the Sockets API and not the Rfcomm API, and so is omitted here for
    // brevity.



© 2016 Microsoft