We have a Custom Action to run an extra setup dialog window after the installation of a program we packaged in. User requirements have now changed and no longer require that custom setup step, but we intend to keep that lying around.
There appears to be no direct feature to disable Custom actions. We have to completely delete it. If we need to revert, it means having to recreate the Custom Action again with all its properties. This seems fine for just one, but I cannot imagine what if we have several Custom actions.
Is there a way (that does not seem obvious) for VS.NET 2003 to actually disable instead of delete?
The melody of logic will always play out the truth. ~ Narumi Ayumu, Spiral