In-Depth

Choosing the Right Client/Server Communication Option

Simplify your development process in n-tier client/server systems with Windows Communication Foundation.

 Listen to the audio and watch the slides! (Running time: 1 hour, 1 minute)

Get help deciding how to select the appropriate client/server communication technology for your development processes. How do you choose from Web services, Web Services Enhancements (WSE), Enterprise Services, Remoting, Distributed Component Object Model (DCOM), and Microsoft Message Queuing (MSMQ)? What does Windows Communication Foundation (WCF), formerly Indigo, mean to you, and how can you plan ahead for a process transition? Rockford Lhotka outlines the strengths and weaknesses of each option for today's developer. Learn why migrating to WCF can simplify your dev processes, and how you can do it smoothly.

About the Author

Rockford Lhotka is the author of several books, including the Expert VB and C# 2005 Business Objects books and related CSLA .NET framework. He is a Microsoft Regional Director, MVP and INETA speaker. Rockford is the Principal Technology Evangelist for Magenic, a Microsoft Gold Certified Partner.

comments powered by Disqus

Featured

  • 'Dev Home' Update Leads Developer Goodies in AI-Powered Windows 11 Update

    Along with today's new AI-powered Windows 11 update come new goodies for developers, including a new edition of Dev Home, a preview offering described as a "control center" providing coding-focused features and functionality.

  • Community Dev Gives VS Code Python Some YAPF

    The latest update to Python in Visual Studio Code includes a new extension for Python formatting that was contributed by a member of the open source community.

  • Devs Demand Visual Studio 2022 Ditch Old .NET Framework Dependencies

    Developers commenting on a Microsoft post about performance improvements in the upcoming .NET 8 demanded the company end Visual Studio 2022's dependency on the old .NET Framework.

  • Microsoft Remakes Azure Quantum Dev Kit with Rust, 'and It Runs in the Browser!'

    "The' tl;dr' is that we rewrote it (mostly) in Rust which compiles to WebAssembly for VS Code or the web, and to native binaries for Python."

Subscribe on YouTube