Lost Password? No account yet? Register
Member Area

Software Installation Technologies

May 17th

Home arrow Community arrow External Forums arrow Windows Installer

Windows Installer
microsoft.public.platformsdk.msi Google Group


  • Re: How to force setup.exe while allowing uninstall, repair from A
    Adding quotes around the ALLs did the job. (Microsoft's going to have to fix
    its documentation so newbies like me don't keep getting confused. In the
    documentation for the REMOVE property, it states:
    To determine whether a product has been set to be completely
    uninstalled, a package author may use a conditional expression to check

  • Re: How to force setup.exe while allowing uninstall, repair from A
    Hi,
    Which means:
    IS PROBABLY FALSE (at least I think the double quotes are required)
    IS FALSE
    IS FALSE
    The log will also show whether or not the custom action was called, double check
    as it could be the custom action is starting but failing. Also properties can change
    value during install so worth checking for this also.

  • Re: VS 2003 Install Projrect, Custom Folder
    Thanks Phil, that solved the problem.

  • Re: VS 2003 Install Projrect, Custom Folder
    This is a Visual Studio build issue, not an MSI thing. You just need to put
    some made-up property name in there that is not going to be initialized,
    then it will build. The install location will default to TempFolder because
    that made-up property name has no value.

  • VS 2003 Install Projrect, Custom Folder
    This is the 1st time I have tried to create an msi file in VS 2003 and
    everything appears to be OK except for one thing. I created a Custom Folder
    which contains 'Banner.bmp' and 'Splash Screen.bmp' used by the Installer.
    The Properties window for the Custom Folder contains the following entries:

  • Re: How to force setup.exe while allowing uninstall, repair from A
    When I use the following command line:
    msiexec.exe /x "my product.msi" REMOVE=ALL
    Property(S): REMOVE = ALL (this line copied from the log file)
    REINSTALL and BOOTSTRAP are not set.

  • Re: How to force setup.exe while allowing uninstall, repair from A
    Hi,
    Are you logging this? What are the values of the properties:
    [link]
    Bye,
    Dennis
    Dennis Bareis [Microsoft MVP] (dbar...@KillSpam.gmail.com)
    [link]
    Freeware Windows Installer creation tool (+ "ORCA automation"):
    [link]

  • Re: How to force setup.exe while allowing uninstall, repair from A
    OK, I don't know what was going on before, but I tried it without the
    property names followed by the ANDs, and the equivalences test as FALSE now
    (as I would expect). I still can't get an uninstall or repair to go ahead
    without also putting BOOTSTRAP=1 on the command line, though.

  • Re: How to force setup.exe while allowing uninstall, repair from A
    I've tried it with and without quotes around the ALL. (And the documentation
    of the REMOVE property says "a package author may use a conditional
    expression to check whether REMOVE=ALL." Note the lack of quotes.)
    As for the property names before the ANDs, I've found that if I don't have
    them, my equivalence checks (BOOTSTRAP = 1, etc.) tend to come out TRUE if

  • Re: So what really happens when you publish SetTargetPath?
    [Please do not mail me a copy of your followup]
    Tony <ton...@gmail.com> spake the secret code
    <8c847589-a0db-4c97-8935-1c745 01d1...@27g2000hsf.googlegroup s.com> thusly:
    The reason that SetTargetPath has a level of indirection to it is so
    that you can reuse the same "browse for folder" dialog for many


[ Back ]

DevInstall's Recent

Visitors: 501097

Extended Menu

MSI 4.0: Latest Blogs