Just double checked:

The new version of the installer is higher than the old installer; the version 
of the new main application is higher than the old version of the main 
application.

So I think this is not about the version, but I don't know.

Also, can you tell me if my code for FilesInUse correct? I found this: 
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html 
There are quite a few other DialogRef listed:
      <DialogRef Id="ErrorDlg" />
<DialogRef Id="FatalError" />
<DialogRef Id="FilesInUse" />
<DialogRef Id="MsiRMFilesInUse" />
<DialogRef Id="PrepareDlg" />
<DialogRef Id="ProgressDlg" />
<DialogRef Id="ResumeDlg" />
<DialogRef Id="UserExit" />
Should I do the same thing?

Anyways, if you know anything about FilesInUse, please let me know.

Thanks.
/Brian



________________________________
From: little.forest <little.for...@ymail.com>
To: General discussion for Windows Installer XML toolset. 
<wix-users@lists.sourceforge.net>
Sent: Friday, October 2, 2009 2:42:41 PM
Subject: Re: [WiX-users] How to add FilesInUse support

Hi Phil,


Thanks for you reply.

It's good to know that "2753 is nothing directly related to FilesInUse". 

For "It's typically caused by running a custom action referring to a program 
that is not going to be installed.  So it looks like you're asking to run 
MainApp but the one in your setup isn't being installed." - It's true. We do 
have a custom action like this(Does this code look okay?):
<CustomAction Id="ExecBootloader_Cmd"
FileKey="MainApp"
ExeCommand="-bootload"
Execute="deferred"
Return="ignore"
HideTarget="no"
Impersonate="no" 
/>

<InstallExecuteSequence>
<Custom Action="ExecBootloader_Cmd" Before="InstallFinalize" />
</InstallExecuteSequence>


As long as the old version wasn't running, the major upgrade worked fine. I 
mean, there wasn't error, the old version was removed, and the new version was 
installed. The custom action run okay as well. But, if the old version was 
running, we did see something different: we see the FilesInUse dialog, we 
shutdown the old version manually, so far so good, we kept it going.. then it 
failed. I noticed the application folder under "Program Files" was not even 
created. Netherless to say, anything new version wasn't installed. So when the 
custom action was triggered, the program can't be found, then error. So in 
here, it seems to me that the only difference is whether "the old version is 
running" and further "FilesInUse". 

So for "This can because there's a component or feature state that means it's 
not being installed, or yours isn't being installed because there's already one 
on the system with a higher version." - I doubt if it's about the version 
higher/lower. Because if this is true, then we couldn't explain why the new 
version was installed and run okay while the old version wasn't running. It's 
suppposed to fail even the old version wasn't running, right? 

Again, the only difference is the "old version running". If not running, no 
FilesInUse showing up, things are okay. If running, the FilesInUse part behave 
correctly but nothing will be installed. So I guess this is about FilesInUse. 
But, really, I don't know the reason and the solution.

By the way, we use WiX version 3.0.4805.0.

If you have any idea, please let me know.

Thanks a lot.

/Brian




________________________________
From: "Wilson, Phil" <phil.wil...@wonderware.com>
To: General discussion for Windows Installer XML toolset. 
<wix-users@lists.sourceforge.net>
Sent: Friday, October 2, 2009 1:57:16 PM
Subject: Re: [WiX-users] How to add FilesInUse support

2753 is nothing directly related to FilesInUse - look up the Windows SDK 
Windows Installer errors for this kind of thing.  

It's typically caused by running a custom action referring to a program that is 
not going to be installed.  So it looks like you're asking to run MainApp but 
the one in your setup isn't being installed. This can because there's a 
component or feature state that means it's not being installed, or yours isn't 
being installed because there's already one on the system with a higher 
version. 

Phil Wilson 


-----Original Message-----
From: little.forest [mailto:little.for...@ymail.com] 
Sent: Friday, October 02, 2009 12:07 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to add FilesInUse support

Let me correct something a bit:

If not add "<DialogRef Id="FilesInUse" />" line, the installation is okay but 
it won't detect and show "FilesInUse" dialog.
If add "<DialogRef Id="FilesInUse" />" line in code, the installation is okay 
if this is a fresh intallation(fresh means no previous version installed). 
If add "<DialogRef Id="FilesInUse" />" line in code, and there is the old 
version application running, then the installation of the new version will 
detect and show the "FilesInUse" dialog which is good. But later on the 
installation of the new version will be failed because of an Error called 2753. 
Why this happens? How to resolve it?

Thanks.



________________________________
From: little.forest <little.for...@ymail.com>
To: wix-users@lists.sourceforge.net
Sent: Friday, October 2, 2009 11:17:01 AM
Subject: [WiX-users] How to add FilesInUse support

We use WiX 3.0.

We have a problem: the end user is running the old version of the application, 
but she tries to install the new version at the same time. As we use major 
upgrade, the old version will be uninstalled first. So in this case, if the old 
version is running, we can't install the new version properly.

I knew "util:CloseApplication". So I tried that. But in our application, there 
is a requirement "close application will just minimize the GUI to system tray 
just like Yahoo Messenger". I'm not sure if "util:CloseApplication" does send 
WM_CLOSE message to our application. But even if it does, our application will 
just minimize itself to system tray but not close itself. We already tested it. 
The application didn't shut down. So we can't use this "util:CloseApplication".

Then I tried another solution: 
http://n2.nabble.com/Custom-action-sequencing-problem-td709311.html#a709311 
Well, it partly worked. If we keep the old version running, then the process is 
killed when installing the new version. However, just a few seconds later, the 
installation failed because of "Error code 2753". I realized the old version 
was uninstalled, the new version wasn't installed. Also, I was thinking killing 
a process directly might not be a good thing. So I kept searching other 
solutions.

Then I found someone said "FilesInUse". I think this solution even works for 
us. So I added this line:
<UI>
<DialogRef Id="FilesInUse" />
...
</UI>

Now we have new problem "Error code 2753". I tried two cases: 
Case 1: I kept the old version running, and I installed the new version. During 
installation, the "FilesInUse" dialog did show up - I was very happy. Then I 
exited the old version. The installation kept going.. just a few seconds, it 
failed. I noticed the old version was uninstalled, but the new version wasn't 
installed. Here is the log:
MSI (s) (48:4C) [10:15:34:839]: Note: 1: 2753 2: MainApp 
MSI (s) (48:4C) [10:15:34:839]: Note: 1: 2205 2:  3: Error 
MSI (s) (48:4C) [10:15:34:839]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` 
FROM `Error` WHERE `Error` = 2753 
DEBUG: Error 2753:  The File 'MainApp' is not marked for installation.
The installer has encountered an unexpected error installing this package. This 
may indicate a problem with this package. The error code is 2753. The arguments 
are: MainApp, , 
MSI (s) (48:4C) [10:15:44:245]: Note: 1: 2205 2:  3: Error 
MSI (s) (48:4C) [10:15:44:245]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` 
FROM `Error` WHERE `Error` = 1709 
MSI (s) (48:4C) [10:15:44:245]: Product: BigAppleProduct -- The installer has 
encountered an unexpected error installing this package. This may indicate a 
problem with this package. The error code is 2753. The arguments are: MainApp, 
, 
The log says error, but what the error means? What caused this error? The log 
didn't say.

Case 2: do a fresh installation. There is no "FilesInUse" dialog showing up, of 
course. But the install still failed - Error 2753. This doesn't make any sense. 

It seems the problem is this new added line "<DialogRef Id="FilesInUse" />". By 
adding this line, the error 2753 is introduced. Why is that? So how can I add 
this FilesInUse support in WiX 3? Where I did wrong here? 

Many many thanks.
/Brian


      __________________________________________________________________
Looking for the perfect gift? Give the gift of Flickr! 

http://www.flickr.com/gift/
------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



      __________________________________________________________________
The new Internet Explorer(r) 8 - Faster, safer, easier.  Optimized for Yahoo!  
Get it Now for Free! at http://downloads.yahoo.com/ca/internetexplorer/
------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



      __________________________________________________________________
Looking for the perfect gift? Give the gift of Flickr! 

http://www.flickr.com/gift/
------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



      __________________________________________________________________
Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your 
favourite sites. Download it now
http://ca.toolbar.yahoo.com.
------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to