As a matter of fact Microsoft Windows services, formerly known as NT services enable you to create long-running executable applications that run in its own Windows session, which then has the ability to start automatically when the computer boots and also can be manually paused, stopped or even restarted. 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. Windows services don’t have any interface to the user, so it cannot be debugged like any regular application, but it’s debugged as a process. .NET has a very nice tool that enables processes debugging while it’s in the run status, by easily pressing Ctrl + Alt + P shortcut. You can then use the Services Control Manager to start, stop, pause, resume, and configure your service. Different from other applications, the service executable must be installed before it can work. You must create an installation component for the service, which installs and registers the service, and creates its entry with the Services Control Manager.
In our project we intend to apply the use of window service and create a window form using Visual Basic.net and Visual Studio 2010. The project will include the following features: It have the ability to evaluating performance of the PC
It can monitor the PC Hard Disk for CRC error
It can evaluate the of RAM (Random Access Memory)
And diagnose problems that are low level to the user
All this will be displayed through the window form attached to it. Since the logic process is done in the service and cannot be seen, the window form will display the messages be it error or normal system message.
For your notice:
This is a short footnote of the proposal however you can add to this...