What does "install in the temp directory" mean? Did you explicitly install
it there, or is it being extracted into the temp directory (which is the way
some custom actions work) and failng to run? Does it work if the first thing
in your code is a MessageBox?
The normal way to do this is to just run a custom action after
InstallFinalize, or tie the custom action to clicking the Finish button. The
fact that you're doing a Commit custom action (which doesn't work in some
disable rollback scenarios anyway) tells me you're probably using a Visual
Studio setup. Your custom action should work fine as an Install custom
action, an executable, assuming it has no dependencies on assemblies you're
installing into the GAC.
--
Phil Wilson
[Microsoft MVP-Windows Installer]
"Leroy" <leroy.lemon[ at ]gmail.com> wrote in message
news:uflhhMkvHHA.4520[ at ]TK2MSFTNGP02.phx.gbl...
[Quoted Text] > Here's my problem.
> I have a scenario where we need to update the data client on a number of
> computers running xp on our domain (oracle stuff).
>
> I've written an assembly in dot net 2k5 that will check the version of the
> client and either remove/install or do an upgrade.
>
> The assembly works fine on it's own, but I need to package it so that it
> runs when the msi is finished installing.
> We plan on releasing the package to the domain using a gpo with elevated
> priveleges.
>
> I've tried setting up the assembly as a custom action to run on commit,
> but all that happens is the file installs into my temp directory with no
> action.
>
> Any suggestions?
>
> Thanks.
>
>
|