Skip to content

Latest commit

 

History

History
61 lines (48 loc) · 2.3 KB

windows_setup.md

File metadata and controls

61 lines (48 loc) · 2.3 KB
Raw

This document is known to be out of date

How to build the Windows sample

The following procedure describes the process of building and running the Event Hubs SDK samples (send and send_batch) on a Windows desktop machine.

Create an Event Hub

To run the sample applications you will need an Event Hub to which they can send messages.

To configure an Event Hub, see Create an Event Hub. Be sure to make a note of the Event Hub name and the SendRule and ReceiveRule connection strings; you will need them to complete building the samples.

Install the SDK

Download the SDK to the board by issuing the following Git command in a terminal Window:

git clone --recursive https://github.com/Azure/azure-event-hubs.git

You will be prompted for your GitHub username and password -- if you have two-factor authentication enabled for your account, you'll need to generate/use a personal access token in place of your password.

To build the Windows samples

  1. In Visual Studio 2013, open the solution for the samples you want to build. The Visual Studio solution files are located in:
\azure-event-hubs\c\eventhub_client\samples\send\windows

or

\azure-event-hubs\c\eventhub_client\samples\send_batch\windows

  1. Update the Event Hub connection information in the sample application. Save your changes.

  2. Rebuild the sample project (right-click the project and click Build).

  3. Press F5 to run the sample application, or after a successful build, run the executable located in the directory:

\azure-event-hubs\c\eventhub_client\samples\send\windows\Win32[Debug|Release]

or

\azure-event-hubs\c\eventhub_client\samples\send_batch\windows\Win32[Debug|Release]

Note: The tools folder in this repository includes the CSharp_ConsumeEventsFromEventHub C# application that can receive messages from an Event Hub. This is useful to help you verify that the samples are sending messages correctly to the Event Hub.