Using Interfaces In .NET Remoting

Conclusion

Running the completed example

Run the server application we created in step 2 by double clicking the .exe file we created. Then run the client application by double clicking the .exe file created in step 3. If all goes well, you should see the formatted resume output.

Conclusion

Interfaces are the preferred way to access .NET remote objects. They enable the developer to create clean code with a complete seperation between client side use of remote objects and the server side implementation. In most cases it is a good idea to use a DLL for your interfaces, another DLL for your implementation in order to maximize reuse potential.

You might also like...

Comments

About the author

David Talbot United States

David Talbot is an experienced Software Architect with a diverse background including creating network applicances, working with television set top boxes, building Billing/CRM systems, Web Port...

Interested in writing for us? Find out more.

Contribute

Why not write for us? Or you could submit an event or a user group in your area. Alternatively just tell us what you think!

Our tools

We've got automatic conversion tools to convert C# to VB.NET, VB.NET to C#. Also you can compress javascript and compress css and generate sql connection strings.

“Measuring programming progress by lines of code is like measuring aircraft building progress by weight.” - Bill Gates