Application Version upgrade

Hi All,
I want to upgrade existing application version from ProductVersion =
1.0.118.1 to ProductVersion = 1.0.154.1
Msi's have the same product and upgrade code.

To upgrade application we are running an application which executes msi with
command line parameters
msiexec / fvomus msiName /norestart /log logfile

Msi includes 2 custom actions:
1. Immediate custom action to stop a windows service application (MB) to
release DLLs
2. Deferred action to start MB

<Custom Action="SetDebugMode" Before="InstallFinalize">DBUG OR DEBUG OR
DBG</Custom>
<Custom Action="AddCarrier" After="SetDebugMode">TASK AND SITEID</Custom>
<Custom Action="StopMB" Before="InstallValidate"></Custom>
<Custom Action="StartMB" After="AddCarrier"></Custom>

The last line of msi log file says: Configuration completed successfully.
But old version assembly is in the application folder. I don't see any logs
entry that would tell me what files overwritten or skipped.

Any suggestions welcome.

Thanks
Vladimir

"Vladimir" <iahnenco@yahoo.com> wrote in message
news:%23%23MvQjp9KHA.5412@TK2MSFTNGP06.phx.gbl...
> Hi All,
> I want to upgrade existing application version from ProductVersion =
> 1.0.118.1 to ProductVersion = 1.0.154.1
> Msi's have the same product and upgrade code.
> To upgrade application we are running an application which executes msi
> with command line parameters
> msiexec / fvomus msiName /norestart /log logfile
> Msi includes 2 custom actions:
> 1. Immediate custom action to stop a windows service application (MB) to
> release DLLs
> 2. Deferred action to start MB
> <Custom Action="SetDebugMode" Before="InstallFinalize">DBUG OR DEBUG OR
> DBG</Custom>
> <Custom Action="AddCarrier" After="SetDebugMode">TASK AND SITEID</Custom>
> <Custom Action="StopMB" Before="InstallValidate"></Custom>
> <Custom Action="StartMB" After="AddCarrier"></Custom>
> The last line of msi log file says: Configuration completed successfully.
> But old version assembly is in the application folder. I don't see any
> logs entry that would tell me what files overwritten or skipped.
> Any suggestions welcome.
> Thanks
> Vladimir

Your logfile is certainly sparse if you used /log as your parameter to
msiexec. Retry your test but use verbose logging instead.

msiexec / fvomus msiName /norestart /l*v logfile

You should see whole section in the log related to InstallFiles and
PatchFiles and from that you should be able to draw more conclusions as to
why your assembly did not get updated after your minor upgrade.

Sincerely,
Adrian Accinelli

Hi,
try
msiexec / fvamus msiName /norestart /log logfile
instead of
msiexec / fvomus msiName /norestart /log logfile


On May 18, 9:25*pm, "Adrian Accinelli"
<hclnospamal...@newsgroup.nospam> wrote:
> "Vladimir" <iahne...@yahoo.com> wrote in message
>
> news:%23%23MvQjp9KHA.5412@TK2MSFTNGP06.phx.gbl...
>
>
>
>
>
> > Hi All,
> > I want to upgrade existing application version from *ProductVersion =
> > 1.0.118.1 to *ProductVersion = 1.0.154.1
> > Msi's have the same product and upgrade code.
> > To upgrade application we are running an application which executes msi
> > with *command line parameters
> > msiexec / fvomus msiName /norestart /log logfile
> > Msi includes 2 custom actions:
> > 1. Immediate custom action to stop a windows service application (MB) to
> > release DLLs
> > 2. Deferred action to start MB
> > <Custom Action="SetDebugMode" Before="InstallFinalize">DBUG OR DEBUG OR
> > DBG</Custom>
> > <Custom Action="AddCarrier" After="SetDebugMode">TASK AND SITEID</Custom>
> > <Custom Action="StopMB" *Before="InstallValidate"></Custom>
> > <Custom Action="StartMB" After="AddCarrier"></Custom>
> > The last line of msi log file says: *Configuration completed successfully.
> > But old version assembly is in the application folder. I don't see any
> > logs *entry that would tell me what files overwritten or skipped.
> > Any suggestions welcome.
> > Thanks
> > Vladimir
>
> Your logfile is certainly sparse if you used /log as your parameter to
> msiexec. *Retry your test but use verbose logging instead.
>
> * * msiexec / fvomus msiName /norestart /l*v logfile
>
> You should see whole section in the log related to InstallFiles and
> PatchFiles and from that you should be able to draw more conclusions as to
> why your assembly did not get updated after your minor upgrade.
>
> Sincerely,
> Adrian Accinelli- Hide quoted text -
>
> - Show quoted text -