| C# Browser History Monitoring Application (Part 1) |
| C#Today |
| The application developed by Jan Narkiewicz in this article monitors the browser history file of a currently logged in user. As the user surfs the web, the contents of their browser history folder are mirrored to a secure location. Inside the mirrored location (only accessible to administrators on the machine) all additions and updates to the users browser history folder are recorded. Deletions are not recorded. The idea is to monitor a users web surfing habits without letting them know their surfing habits are being monitored. |
|
| C#: A Message Queuing Service Application |
| MSDN |
| This article outlines a Windows service solution designed to process several message queues, focusing on the application of the Microsoft .NET Framework and C#. |
|
| Create and Control Windows Services |
| Visual Basic Programmers Journal |
| Windows Services (formerly known as NT Services) can seem overwhelming and daunting to the uninitiated because of a vast array of callback functions and long parameter lists. Even though creating services in C++ almost ensures top-notch performance, the complexity factor might outweigh that fact. However, with the recent release of the .NET Framework SDK, the complexity of creating and controlling services has diminished. |
|
| Creating a Singleton Service with Visual Studio .NET |
| MSDN |
| A common design pattern that I've seen used is the creation of a COM singleton that resides in a service. A service is a long-running executable that does not support a user interface, and which might not run under the logged-on user account. The service can run without any user being logged on to the computer. This makes services ideal for use on a server or whenever you need functionality that does not interfere with other users who are working on the same computer. |
|
| Developing a Windows SERVICE Application using .NET Framework with C#. |
| The Code Project |
| An Introduction to Windows SERVICE Application using .NET Framework |
|
| Distributing Objects in Visual Basic .NET |
| MSDN |
| The challenge we have faced in the past is that it isn't always easy to give a developer an object, especially across the network. Objects in COM are always passed by reference, meaning that the COM object remains in the process and on the machine where it was created. The client code merely gets a reference to the object, so each method call is marshaled across the network, back to the original object to be serviced. With Microsoft .NET, we have the option of passing our objects either by reference like COM, or by value. When an object is passed by value, we not only get a copy of the data, but we get an actual instance of the object on our client workstation. The object itself physically moves from the server machine to our client machine, meaning that our client application not only has the data we need, but we have the business logic relating to that data as well. |
|
| How To Host .NET Remoting Objects In Windows Service |
| The Code Project |
| For sometime I have been working on Remoting projects using .NET but every time I will always end up creating a console application to run as a remote server and host the remoting object in that. This definitely is not going to be case in real world applications. Most of the time you will require that your remote object is hosted in a server that is running all the time and does not require any user intervention like in Console application. |
|
| How to write a Windows Service |
| The Code Project |
| Remember how difficult was to create a Windows Service in Visual Studio 6? You had to create a wrapper for your programs in order to do that if you wanted to added to existing programs you had. With C# is easy, maybe too easy for me to spend time. Create a new project as select C# Windows Service in your .NET Editor. A template class should include almost everything you need. |
|
| Introduction to Windows Service Applications |
| MSDN |
| Microsoft Windows services, formerly known as NT services, enable you to create long-running executable applications that run in their own Windows sessions. These services can be automatically started when the computer boots, can be paused and restarted, and do not show any user interface. This makes services ideal for use on a server or whenever you need long-running functionality that does not interfere with other users who are working on the same computer. You can also run services in the security context of a specific user account that is different from the logged-on user or the default computer account. For more information about services and Windows sessions, see the "About Services" section in the Platform SDK documentation in MSDN Online. |
|
| Windows Services Simplified in .NET - Part 1 |
| DotNetJunkies |
| Keyuan shows you how easy it is to create Windows services with the .NET Base Class Library in any .NET language. |
|
| Windows Services Simplified in .NET - Part 2 |
| DotNetJunkies |
| In Part 1, Keyuan discussed how to create service applications and how to install the service apps using the project installer class. In Part 2, he will cover how to create a Service Control Program (SCP), a separate executable, that provides an UI to communicate with and control the service app. |
|
| Windows Services: New Base Classes in .NET Make Writing a Windows Service Easy |
| MSDN |
| Windows services are applications that run outside of any particular user context in Windows NT, Windows 2000, or Windows XP. The creation of services used to require expert coding skills and generally required C or C++. Visual Studio .NET now makes it easy for you to create a Windows service, whether you're writing code in C++, C#, or Visual Basic. You can also write a Windows service in any other language that targets the common language runtime. This article walks you through the creation of a useful Windows service, then demonstrates how to install, test, and debug the service. |
|