Current tendency to ship even smallest apps (like simple games, tools, etc) with .msi or even with .exe that can do virtually anything is very annoying. After app is installed it is run as standard user, but it is useless if during installation it can do what it wants.

For example configuring fire wall, maybe I do not want to that my new shiny 15kB calculator application have full access to the Internet (for incoming connections :) )

Custom actions inside msi are even worse, since it is possible to run custom function inside provided dll!

How do you manage to handle this, just ignore problem, or maybe have some unknown for me methods of running msi packages? And from other side, why the hell every body is know making installers? In many many cases simple zip file will be enough at least as a opportunity to standard installer.

The current tendency to ship even the smallest applications (like simple games, tools, etc.) as a Windows Installer (.msi) or even with .exe that can do virtually anything is very annoying. After the application is installed it is run as standard user, but it is useless if during installation it can do what it wants.

For example, configuring a firewall, maybe I do not want my new shiny 15 KB calculator application to have full access to the Internet (for incoming connections :) )

Custom actions inside Windows Installer installer files are even worse, since it is possible to run a custom function inside the provided DLL file!

How do you manage to handle this, just ignore problem, or maybe have some unknown for me methods of running Windows Installer packages? And from the other side, why on Earth is everybody making installers? In many many cases, a simple ZIP file will be enough, at least as a opportunity to a standard installer.