Creating Microsoft-Based Interoperable Solutions for a Digital Government
Microsoft Government Solutions, January 23, 2006 (not available online)
Government organizations constantly seek ways to improve service and cut costs. Increasingly, they look to standards-based technologies to help. Now governments can deliver innovative, cost-effective business solutions to their constituents using a Microsoft .NET strategy to help integrate their diverse environments. Tarak Modi, an executive architect at Unisys, recently led one such highly successful effort. His team used Services Oriented Architecture (SOA) and Web services on a .NET platform to create an interoperable e-government application, building on a state agency's legacy systems to deliver new services to citizens. Modi describes his team's work and the results they achieved in a white paper published by Microsoft.

Crosscutting Your Web Services Security
Visual Studio Magazine, November 1, 2004
Learn to build a robust, flexible, and secure Web services architecture that leverages the .NET Framework's existing capabilities and handles security as a crosscutting concern.

Plug Into J2EE-.NET Interoperability
FTP Online (J2EE Special Issue), June 2004
It's all about platform neutrality: Your J2EE and .NET apps must interact. This overview presents the standards and available technologies that can help you shape interoperable solutions.

.NET Security Explained: ASP.NET Security
Hardcore Visual Studio .NET, August, 2002 (not available online)
In this article, Tarak Modi provides a detailed look at how security works in ASP.NET and how it interacts with the security in Internet Information Server (IIS). Then he demonstrates an example of implementing form authentication and shows how it dovetails with standard role-based security in .NET.

.NET Security Explained, Part 3: Role-Based Security
.NET Developer, July, 2002(not available online)
Just as code-access security revolves around the identity of the code, role-based security revolves around the identity of the user executing the code. Role-based security provides a way to perform and enforce user authorization in which only certain users are allowed to perform certain operations. In this article, Tarak Modi explains how this process works.

.NET Security Explained, Part 2: Code-Access Security
.NET Developer, June, 2002(not available online)
In this second installment of the series ".NET Security Explained," Tarak Modi dives into code-access security. He creates an example program and makes it work within the bounds of a more restricted code-access security model than that granted by the default .NET Framework to locally loaded code.

.NET Security Explained: The Basics
.NET Developer, May, 2002 (not available online)
The first in a series of four articles taking an in-depth look at Security in the .NET Framework.

.NET Remoting Explained: Declarative .NET Remoting
.NET Developer, March, 2002 (not available online)
This is the fourth and final installment in Tarak Modi's series of articles on .NET Remoting. In the first part of this series, he introduced the basic concepts behind .NET Remoting, including AppDomains and contexts. In the second installment, he discussed server-activated remote objects, and in the third one, client-activated objects. If you missed any of these articles, they're all available to subscribers in the "View Past Ossues" section of the .NET Developer Web site. In this final installment, Tarak explores two key aspects of .NET Remoting: configuration files and IIS hosting.

.NET Remoting, Part 3: Client-Activated Objects
.NET Developer, February, 2002 (not available online)
This is the third article in Tarak Modi's coverage of .NET Remoting. In his first article (see the December 2001 issue), he introduced the basic concepts behind .NET Remoting including the .NET Remoting architecture, AppDomains, and contexts. In the second he discussed server-activated remote objects, starting with a little bit of theory and wrapping up with a complete working example. This month, Tarak will talk about client-activated objects and their lifetime management.

.NET Remoting, Part 2: Server-Activated Objects
.NET Developer, January, 2002(not available online)
This is the second article in Tarak Modi's coverage of .NET Remoting. In his first article (see the December 2001 issue), he introduced the basic concepts behind .NET Remoting including the .NET Remoting architecture, AppDomains, and contexts. This month he discusses server-activated remote objects, starting with a little bit of theory and wrapping up with a complete working example.

.NET Remoting, Part 1
.NET Developer, December, 2001 (not available online)
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.