I have a VS 2003 .NET setup project with multiple custom actions in
both the install and rollback phase. Some of these custom actions
allow the user to cancel the installation (by throwing an
InstallException) in which case a rollback will occur.
The problem is that due to the premature cancellation of the
installation, some of the install custom actions are never executed,
thus when the corresponding rollback CAs are called, the savedState
file cannot be located and an error message about missing savedState
files is being displayed for each of those custom actions.
Is there any mechanism in VS 2003 .NET for calling the rollback()
method only on those classes for which install() had previously been
called? Or alternatively, is there a way to suppress these annoying
error messages about missing savedState files? Any help would be
greatly appreciated ...
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
savedState errors when cancelling installation
Started by
ekim2000
, Jun 17 2004 15:53
1 reply to this topic
Neo
-
- Members
- 48 posts
Posted 19 August 2004 - 11:04
Yeah.. they are pretty nasty ones. Make sure that the assemblies are SNed. Also ensure that the MsiAssembly and the MsiAssemblyName for all these assemblies have been correctly populated. Orca should help you in all this. I havent had much success with the VS Installer on these but InstallShield DevStudio or X offers much more control over the contents going in to these directories. But on the flip side, you would not be able to control the destination of the dependent assemblies that have been detected.