.NET news » Search results

This article demonstrates a quick and easy-to-use implementation for cross-AppDomain communication in .NET by leveraging Windows native messaging. The XDMessaging library is based on code developed to aid rapid development for a recent Vista project that required a lot of cross-AppDomain communication in a locked-down environment. It proved to be extremely useful in a number of scenarios where .NET Remoting would have been impractical, if not impossible, and actually solved more problems than I could have imagined due to its simplicity. The library is intended to send messages between multiple applications in a same-box scenario. For example, a task-tray application might want to communicate with or monitor a separate desktop application. The library does not implement cross-domain communication across a network, for which case .NET Remoting is sufficient.

Windows Communication Foundation simplifies the creation of transactional services.

Windows Communication Foundation (WCF) provides numerous extensibility points that allow developers to customize the runtime behavior for service dispatching and client proxy invocation. You can tap into these extensibility points by writing custom behaviors that can be applied declaratively to your services. This article shows how this process works.

Windows Management Instrumentation (WMI) is Microsoft's implementation of Web-Based Enterprise Management (WBEM) and the Common Information Model (CIM). Although WMI is COM-based, Andriy Klyuchevskyy shows you how you can access it from C# and VB.NET through System.Management, thanks to COM Inter-Op.

Windows Communication Foundation (WCF) enables disconnected work between clients and services. The client posts messages to a queue and the service processes them later. Such interaction permits a different programming model from the default request/response pattern, enabling possibilities such as load leveling, improved availability, and compensating work, to name just a few. This column starts with a brief introduction to Windows Communication Foundation queued calls and then presents an interesting problem-how to get results out of a queued call-and the solution via some cool Windows Communication Foundation programming techniques and a few helper classes.

Windows Communication Foundation unifies the existing suite of .NET distributed technologies into a single programming model to improve the developer experience. This article introduces WCF so you'll be prepared to take advantage of all the new capabilities.

With the advent of .NET Framework 3.0 (formerly WinFX), terms like Windows Presentation Foundation (formerly Avalon), Communication Foundation (formerly Indigo), Workflow Foundation (formerly WWF) and Cardspace (formerly InfoCard) are everywhere. The .NET Framework 3.0 also includes a powerful general-purpose object initialization language known as XAML (eXtensible Application Markup Language). What Microsoft is really putting stress on is creating compelling user experiences and secure, seamless communication across boundaries.

In this series of articles, I will be explaining and going in depth with some of the core components of .NET Framework 3.0.

Let's start with Windows Workflow Foundation (WF)...

Failing to adopt an appropriate testing approach to help identify bugs along the development process can have as devastating an impact on your project as a hurried or non-existent design. Fortunately, automated testing tools like AutomatedQA's TestComplete 5 make the process of creating structured testing affordable and significantly less time-consuming.

Sending email using the Simple Mail Transport Protocol (SMTP) can be a slow process, particularly when sending large numbers of messages using, for example, a bulk email tool. This process can be accelerated with considered use of asynchronous sending.

Starting with this article, we shall explore various aspects of WCF