Software Deployment

Any suggestion?

The solution would involve writing a custom action to prompt for the password if the package were being removed, if the password were wrong- you would abort the removal. Protecting your password may require hiding your custom action code in a DLL- you may be better off basing success on group membership instead. The closest thing to a quick answer here may be this: http://desktopengineertraining.com/msirestrictrun it is designed to restrict execution of an MSI (not removal) but the principal is the same- it should at least set you in the right direction.

Let us know how you decide to handle this!

It seems that I cannot use it(MSI Restrict Run) to prevent somebody from uninstalling my application?
I have look at custom actions. But can a custom action cancle unistallation?
I try custom actions in a deploy project of VS.NET. But it seems that custom actions are triggered AFTER install/uninstall?
May be I need Orca?

Well
Just to say that I have created a custom action with condition "REMOVE=ALL" to resolve the problem.