free pdf417 barcode generator c# s IMPLEMENTING REMOTE DATA PORTAL HOSTS in Visual C#

Drawing PDF 417 in Visual C# s IMPLEMENTING REMOTE DATA PORTAL HOSTS

For most server-side behavior, SingleCall is ideal because each method call is handled by a newly created object that has its own thread. You don t need to worry about threading issues, or about one client interfering with another in some way. Having selected a mode, you need to define the URI that will be used to access the server-side object. This URI is combined with the server name and virtual root to construct a URL that clients can use to call the server. The URL is in the form http://yourserver/yourvroot/testserver.rem, where yourserver is the name of your server and yourvroot is the name of your virtual root.

The .rem extension is important. When ASP.NET is installed on a server, it configures IIS to route .rem and .soap extensions to the remoting subsystem. Either extension will work, as they re both configured to do the same thing.

Finally, you need to tell the remoting subsystem which specific class and DLL this URL refers to. The type attribute is somewhat cryptic because it accepts a string that contains the full name (including namespaces) of the class, a comma, and then the name of the assembly (DLL) that contains the class. Note that the assembly name doesn t include the .dll extension. With the well-known endpoint defined, clients can call the server. However, to allow for full serialization of complex object graphs, remoting must be told to allow any type to be serialized. This is the purpose behind the XML in the <channels> element. This XML sets the typeFilterLevel attribute to Full for both the SoapFormatter and BinaryFormatter in the .NET Framework. As these are the two formatters supported by remoting, this ensures that all serializable objects can flow through to the data portal.

At this point, the application server is configured and is ready for use by clients. The same application server can be used by Windows Forms, Web Forms, and Web Services clients even all at once, if you choose. The only requirement is that both the application server and clients have the same version of your business assemblies installed. To configure a Windows Forms client, you need to edit the app.config file. To configure either a Web Forms or Web Service client, you need to edit the web.config file. In either case, the configuration file should contain the following bold lines: < xml version="1.0" encoding="utf-8" > <configuration> <appSettings> <add key="CslaAuthentication" value="Csla" /> <add key="CslaDataPortalProxy" value="Csla.DataPortalClient.RemotingProxy, Csla"/> <add key="CslaDataPortalUrl" value="http://localhost/RemotingHost/RemotingPortal.rem"/> </appSettings> <connectionStrings> </connectionStrings> </configuration> The CslaDataPortalProxy element specifies that the data portal should use the remoting channel, and the CslaDataPortalUrl element specifies the URL of the server. You ll need to replace localhost with the name (and possibly the TCP port) of your server, and RemotingHost with the name of your virtual root. Also remember that XML is case sensitive, so double-check to make sure you enter the text exactly as shown here.

Of course, web.config should also include the connection strings for the database in the <connectionStrings> element. You can see an example in the code download for the book.

If you do implement a custom remoting host and opt to use the TCP channel rather than the HTTP channel, you can optionally also include the following element within the <appSettings> block: <add key="CslaEncryptRemoting" value="true"/> Adding this element tells the RemotingProxy class to automatically encrypt data sent across the network. This option is not available when using the HTTP channel, so in that case, you should use SSL to secure the channel. At this point, you should understand how to set up an application server to use remoting, and how to configure a client to use that server.