How to create hard to kill app/process in .net?

What is the best way to secure background process/service from killing? I consider creating 2 or 3 services which will watch each other and start when they are stopped.

Do you know a better way to achieve this?

Cheers!

Update: There are some comments which says "dont do that". I don't want to harm a computer or make some kind or virus. There are some situations where you need to do such a thing eg. parental control. I know that operating systems are for users, but I would like to know the best possible way to secure process/service from killing.

Update2: There was a question about use case. The application should monitor and block unwanted websites on children computer. The children should be a开发者_StackOverflow中文版ble to install/uninstall other software so it have to be administrator account.

Perhaps you can explain the use case? There is almost certainly a better solution than using the approach of a malware for any genuinely useful piece of functionality. Without knowing what you're attempting it's hard to advise.

Edit

You would be better off creating a windows service and instructing your parent to install as an administrator, with child accounts being denied permission to modify the service. That way your system administrators (parents) aren't deprived control over their own system.

This could lead to bad behavior and may lead anyone who ran your application to get into safe mode and set the services to disabled upon startup.

It's best to let your users decide which services to run.