Hi AnjuR,
Welcome here!
Something like this:
oid Scenario1::StartListener_Click(Platform::Object^ sender, Windows::UI::Xaml::RoutedEventArgs^ e)
{
// Overriding the listener here is safe as it will be deleted once all references to it are gone. However, in many cases this
// is a dangerous pattern to override data semi-randomly (each time user clicked the button) so we block it here.
if (CoreApplication::Properties->HasKey("listener"))
{
rootPage->NotifyUser("This step has already been executed. Please move to the next one.", NotifyType::ErrorMessage);
return;
}
if (ServiceNameForListener->Text == nullptr)
{
rootPage->NotifyUser("Please provide a service name.", NotifyType::ErrorMessage);
return;
}
StreamSocketListener^ listener = ref new StreamSocketListener();
ListenerContext^ listenerContext = ref new ListenerContext(rootPage, listener);
listener->ConnectionReceived += ref new TypedEventHandler<StreamSocketListener^, StreamSocketListenerConnectionReceivedEventArgs^>(listenerContext, &ListenerContext::OnConnection);
// Events cannot be hooked up directly to the ScenarioInput1 object, as the object can fall out-of-scope and be deleted. This would render
// any event hooked up to the object ineffective. The ListenerContext guarantees that both the listener and object that serves it's events have the same life time.
CoreApplication::Properties->Insert("listener", listenerContext);
// Start listen operation.
task<void>(listener->BindServiceNameAsync(ServiceNameForListener->Text)).then([this] (task<void> previousTask)
{
try
{
// Try getting all exceptions from the continuation chain above this point.
previousTask.get();
rootPage->NotifyUser("Listening", NotifyType::StatusMessage);
}
catch (Exception^ exception)
{
CoreApplication::Properties->Remove("listener");
rootPage->NotifyUser("Start listening failed with error: " + exception->Message, NotifyType::ErrorMessage);
}
});
}
You could get it from here:
http://code.msdn.microsoft.com/windowsapps/StreamSocket-Sample-8c573931
This sample demonstrates the basics of the
StreamSocket class using the networking features provided by the Windows Runtime. The client component of the sample creates a TCP socket to make a network connection, uses the socket to send data, and closes the socket. The server component
of the sample creates a TCP socket to listen for and accept network connections, accepts connections from the incoming socket, uses the socket to receive data from the client, and closes the socket.
Regards!
Xiaoliang
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.
