Working With the Win32 Client

Before working with the Win32 client, run the simple client. The simple client automatically creates system users with which the Win32 client can interact.

The Win32 client does not require any configuration outside the application.

The Win32 client can either connect directly to the ObjectManager object of the remoting server or it can perform all the method calls through the Web service. The Web service forwards the method calls to the ObjectManager object on the remoting server.

Once you connect to the Win32 client, you can either create a new user or log in as an existing user. You can also delete the current user. Any messages sent to the active user are listed in the message store, including any messages sent using the sample Win32 client or the simple client. You can delete messages or send new messages to other users in the system.

The Last Error box shows the error text of the last error that occurred when a method was executed.

Note: When errors occur while calling methods on remote objects, you see error descriptions in the Error Text box.

Navigate to <public user documents>\Silk Performer 20.5\SampleApps\DOTNET\Message Sample\MessageWin32Client and double-click MessageWin32Client.exe. The sample Win32 client starts.
Connect to either the Remoting server or the Web service.
- To log into the .NET Remoting message server, enter the server's URL (for example, http://localhost:1999/ObjectManager.rem) in the Message Server field and click Connect.
- To log into the sample Web service, enter the Web service URL (for example, http://localhost/MessageWebService/MessageService.asmx) in the Web Server field and click Connect.
Login using one of the users that the simple client application created. By default, the simple client application creates User1 with password Pass1 and User2 with password Pass2.
Create a new user.
Login using the newly created login credentials.
Send a message to another user.
Note: User names are case-sensitive.
Review the server console output. Logging information related to all methods that were called is listed there.

Be sure to log out after you finish your work.