The Perfect Service - Part 2
page 1 of 6
Published: 10 Jan 2006
Unedited - Community Contributed
Abstract
In this article, Ambrose explores the code and techniques involved in getting the "Perfect Service" working. See Part 1 of this series for an introduction to the application and how to use it.
by J. Ambrose Little
Feedback
Average Rating: This article has not yet been rated.
Views (Total / Last 10 Days): 27191/ 87

Introduction

Note: This article was originally published in August 2004 on 15Seconds.com, but it has gotten good reviews, and the techniques, I believe, are still valid.  I hope the readers of ASPAlliance find it as useful as I have.

[Download Code]

In the first part of this series, we covered what it is that the .NET Service Manager does as well as how to install and configure managed services to run under it. In this part, we're going to cover the details of how the .NET Service Manager works, that is, how it enables the great features such as drag-n-drop deployment. Many of the concepts behind this can be abstracted to apply to other .NET projects you may work on.

There are a few core technologies that made this facility possible, which are .NET Remoting, AppDomains, Reflection, shadow copy, and other standard object-oriented practices like classes and interfaces. The key technology that enables the dynamic loading and, more importantly, unloading of assemblies is Remoting; it allows us to completely load, host, and run code in an isolated part of memory (an application domain, a.k.a., AppDomain) that for all intents and purposes acts like a standard Windows process.


View Entire Article

User Comments

No comments posted yet.






Community Advice: ASP | SQL | XML | Regular Expressions | Windows


©Copyright 1998-2017 ASPAlliance.com  |  Page Processed at 2017-08-22 7:06:13 AM  AspAlliance Recent Articles RSS Feed
About ASPAlliance | Newsgroups | Advertise | Authors | Email Lists | Feedback | Link To Us | Privacy | Search