Re: Uninstall Custom Action not getting called.

Thanks for the reply. Unfortunately your suggestion seems to have had a
distastrous effect. When I ran msiexec as suggested it hung with a DOS window
open called something like MSI40 - I can't remember the number.

Now I cannot install or uninstall my software from within Visual Studio or
outside it, even if I do a full rebuild.

Any suggestions?

"Phil Wilson" wrote:

Your setup&deployment project has a ProductCode property. Try the uninstall
like this:

msiexec /x {the product code guid} /l*vx somefile.log

to produce a log of the uninstall. There will be something about whether
there was an attempt to call it. Note that Win32 exes have dependencies that
you might not have installed, like the C runtime support, so it will try to
call it but fail.
--
Phil Wilson
[Microsoft MVP Windows Installer]

"TheClothCat" <TheClothCat@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:67CF6E1F-A02A-44F7-B7E2-F53D10300C09@xxxxxxxxxxxxxxxx
Hi everyone,

I want to run an exe (Uninst.exe) when my software is uninstalled. I have
added the file to the Application Folder in the File System Editor and
added
it as a Custom Action under the Uninstall phase in the Custom Action
Editor,
but it does not get executed when my software is uninstalled, either from
within Visual Studio on my development PC or on a different PC when
installed
from a CD.

I have put debug code in Uninst.exe so I am sure it is not getting
executed.
It is a very simple console app written in C++ for Win32. I got it to work
once on the different PC but it would not do it again.

Stranger still, I changed the Permanent Property of Uninst.exe to be True
and the installer correctly left it in the app's directory. However, after
I
changed it back to False it still leaves it there!

It is almost as if Setup uses a cache and the cache is not working
properly.
I'm using Visual Studio 2003 with SP1.

I'm baffled. Any ideas would be welcome.

Thank you.




.

Relevant Pages

  • Re: Upgrading Office 2003 Standard from Office XP Pro
    ... whose permissions does the batfile use to get to the server? ... with OfficeXP SP3 installed, uninstall didn't do squat. ... msiexec, see below. ... msiexec = Windows Installer ...
    (microsoft.public.office.misc)
  • Re: Upgrading Office 2003 Standard from Office XP Pro
    ... with OfficeXP SP3 installed, uninstall didn't do squat. ... msiexec, see below. ... msiexec = Windows Installer ... I've created a batch file that I haven't fully tested yet, ...
    (microsoft.public.office.misc)
  • Re: .NET installer tips needed
    ... u can uninstall a program with this command... ... msiexec /x package.msi ... What other installer integrate into VS2005 as well? ... Installshield work well with .net assemblies and VS2005? ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: How to best communicate with Microsoft about the difficulties of uninstalling the 2007 Office sy
    ... the "uninstall" is supposed to be the automated removal tool...which doesn't always work as intended. ... In my past dealings with folks from Microsoft, I think there are a lot of really smart people who have way too many priorities and PR issues to deal with. ... Automation would be great, though it's always dangerous to automate stuff when you don't know the configuration of everyone's particular system, and the risk of toasting something is pretty high. ... it would be great if the Windows Installer Cleanup Utility would be updated to support Office 2007. ...
    (microsoft.public.office.setup)
  • Re: Windows XP upgrade...virus?
    ... If I could just get Norton uninstalled! ... Needed to uninstall Easy CD Creator, ... > uninstall all of Norton first, and all other virus and system-like software. ... >> When I try to install most everything, I get a Windows Installer ...
    (microsoft.public.windowsxp.help_and_support)