This section describes the instances in the Microsoft. NET services (Dec 2008 CTP) SDK in a short language to show you how to get started with service bus.
If you have not installed the Microsoft. NET services (Dec 2008 CTP) SDK, you can directly download the attachment.
Instance used:
First, open the Visual Studio solution echosample. sln under the Microsoft. NET services (Dec 2008 CTP) SDK \ samples \ servicebus \ gettingstarted \ echo \ cs35 \ directory
Right-click the service project to enable the new instance.
Enter the username and password of the solution. (Set in http://portal.ex.azure.microsoft.com) after the verification is successful, the console will give a URL similar to "SB: // servicebus.windows.net/services/sixsix/echoservice的.
Enable the debugging instance of a client. Similarly, you must enter the solution name and password.
Now the client has been connected to the service of the server.
I believe that everyone knows the role of this service through the solution name. It is very simple to input a string from the customer segment to the server, and the server returns the same string to the client.
View service bus usage through instances:
Obviously, the services used in this instance are the most basic echo services in network programming. We use the username/password authentication method.
Readers can try to disable the server. You will find that the client has not changed, but you cannot call the service or obtain the echo. This indicates that the service bus actually plays a bridging role. ServerProgramRegardless of the network environment in which the service runs, whether in the NAT or public environment, it does not care how the IP address of the service is changed, or even after the service is behind the firewall, the positioning of the client depends on the uniform URI provided by the Service Bus. The service bus provides registration and address resolution for the service. In this example, the echo service address is always "SB: // response. This is a practical feature of service bus as mentioned in the previous section.
In addition, if you open http://servicebus.windows.net/services/#your solution name }/, we can see that service bus has installed all your solution in atom 1.0 feed format in "bus" (only the services that can be used currently are displayed, that is, if you turn off the server program, will not see the content ). The http://servicebus.windows.net/services/sixsix/ is shown below. "Sixsix" is my solution name. Currently, this solution has only one echoservice.
After understanding the usage and purpose of the service bus, it is easy to program the operation. ViewCode.
SDK reader code: http://files.cnblogs.com/azure/ServiceBus.rar Not Installed