I created a custom action for my setup project. The customer action worked fine. Now I get a file called myprogram.InstallState. Why do I get this file? I don't need it. I don't like to create unecessary stuff.
Arne G Tuesday, September 29, 2009 9:12 PM
It's because you used an Installer class. It's used to save state. I don't know what you did in your installer class custom action, but you don't need to use installer classes - there are other types of custom action.Phil Wilson
It's because you used an Installer class. It's used to save state. I don't know what you did in your installer class custom action, but you don't need to use installer classes - there are other types of custom action.Phil Wilson
Thanks for the answer. I created a data directory for my log files in a custom action. Where can I learn more about other types of custom actions?
Arne G Monday, October 05, 2009 2:01 PM
I'm not sure exactly - this seems to be another of the areas that's documented in the Windows Installer documentation, but not described much in Visual Studio. Basically you can run a program (and pass it command line arguments), call a vbscript, and call a C++ Dll. This might help:
index > ClickOnce and Setup & Deployment Projects > what is the used of .InstallState