| .NET Remoting Contexts |
| C#Today |
| In a distributed architecture, disparate components co-operate to perform work, and in such an architecture there needs to be a streamlined infrastructure for providing cross object communication. .NET framework introduces a new one, called .NET Remoting. .NET remoting is the glue that links together components (aka assemblies) in different .NET application domains. In addition to the marshalling of calls across these app domains, the remoting infrastructure also maintains a context for each assembly, and each method call that crosses over assembly boundaries. In this article, Kaushal Sanghavi looks at what contexts are, how they work, and how they can be used to pass data between different objects. |
|
| .NET Remoting Explained |
| http://www.pinnaclepublishing.com/ |
| What if you were told that you had to create an application that was to support several thousand concurrent users, 24x7? And the only choice you had was to create a single, monolithic application that ran on one machine! No matter how big a machine you get, it won't be long before you start pulling your hair out. Luckily, you won't have to do that in the .NET platform—thanks to its distributed computing capabilities. Tarak Modi explains in detail. |
|
| An Introduction to Microsoft .NET Remoting Framework |
| MSDN |
| This article explains the fundamentals of the Microsoft .NET Remoting Framework. In addition to describing the main components that make up the .NET Remoting Framework, this document describes different scenarios in which .NET Remoting could be used to communicate with distributed objects. |
|
| Aspect-Oriented Programming Enables Better Code Encapsulation and Reuse |
| MSDN |
| Aspect-oriented Programming (AOP), a paradigm invented at Xerox PARC in the 1990s, lets the developer better separate tasks that should not be inextricably tangled, such as mathematical operations and exception handling. The AOP approach has a number of benefits. First, it improves performance because the operations are more succinct. Second, it allows programmers to spend less time rewriting the same code. Overall, AOP enables better encapsulation of distinct procedures and promotes future interoperation. |
|
| Declarative Transactions using ADO.NET and Without Enterprise Services |
| The Code Project |
| Sometimes it is nice to prototype up a simple database application. This code may help, by providing the automatic transactional model of COM+ in a non-COM+ environment. This example uses "Interception" to provide automatic transactioning support for non-COM+ classes. |
|
| Make Synchronization Automatic |
| Visual Studio Magazine |
| When adding the [Synchronization] attribute, .NET automatically ensures that only one thread at a time can access the object. .NET automatically associates a synchronization lock with the object, locking it before every method call and unlocking it (to be used by other threads) when the method returns. This is a huge productivity gain, because thread synchronization and concurrency management are among the most common development pitfalls. There is a lot more to this attribute than mere synchronization, including strategies for sharing the lock with other objects, even classes developed by other vendors. This short demo walks you though the steps required to use the attribute in a simple scenario. |
|
| Managed Security Context in ASP.NET |
| MSDN |
| In my November 2001 column I focused on the unmanaged security context that is used in an ASP.NET application. It's very important to choose this security context wisely, as any calls to the operating system or to your own unmanaged DLLs and COM components will run here. This month, I'll focus on the way you can make use of your managed security context. |
|
| Multithreading Part 3: Thread Synchronization |
| C# Corner |
| Gradually, as you start picking up the threads of multi-threading, you would feel the need to manage shared resources. The .NET framework provides a number of classes and data types that you can use to control the access to shared resources. |
|
| Oh Behave! - Attributes in .NET |
| Developer Network Journal |
| According to my old school dictionary, the verb ‘attribute’ means ‘to consider as belonging to’, while the noun means ‘a quality or property inseparable from an item’. In Windows programming, the term ‘attribute’ is used by many technologies, and with the release of the .NET framework you’ll find it used even more. In general, an attribute is a property of an item which forms part of its description and defines some aspect of its behaviour. |
|
| Understanding Enterprise Services (COM+) in .NET |
| MSDN |
| Provides technical details behind the integration of Microsoft .NET and COM+ services and describes the services available to managed code. |
|
