[WiX-users] bootstrapper dialog title in Wix 3.7

2013-05-06 Thread Kyle Lee
Hi,
In Wix 3.6, the following bootstrapper.wxs used to display "Our Product
Patch 2" in the bootstrapper dialog title:

http://schemas.microsoft.com/wix/2006/wi";>
  





  

  


As of Wix 3.7, it doesn't show up in the title. Instead, it only shows
"Setup".
If I add to "Bundle" element, such as,
http://p.sf.net/sfu/appdyn_d2d_ap1
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] upgrade didn't remove the earlier product from ARP

2012-03-29 Thread Kyle Lee
Using Wix 3.5, my initial MSI package (MyProduct v1.0) contained quite a
few features, e.g. MS Word 95/XP/2003/2007/2010, MS Excel
95/XP/2003/2007/2010, MS PowerPoint 95/XP/2003/2007/2010. Their feature
level was initially set to 0 but set to 1 if the specific app existed
(using AppSearch). In other words, if MS Office 2003 was installed, only
Word 2003, Excel 2003 and PowerPoint 2003 features had level=1, and the
rest remained as 0.

Recently I made the upgrade MSI package (MyProduct v2.0) using the same
approach people said, such as, in How to implement WiX installer
upgrade?

And I scheduled *"RemoveExistingProducts" After="InstallValidate"* in *
"InstallExecuteSequence"*.

Here is a fatal flaw in my installer: suppose the user had MS Office 2003
when he installed MyProduct v1.0. Now he upgraded MS Office to Office 2007
(therefore Office 2003 no longer exists), before he upgrades MyProduct to
v2.0. My installer can't handle this. Why? I've tried to remove the old
features (e.g. Word 2003, etc.) using the type 1 custom action by calling
MsiSetFeatureState function. Although that function returned ERROR_SUCCESS,
their states didn't get set to ABSENT but remained as NULL (I know the
feature levels for Word 2003 etc. are 0 since they don't exist any more,
and I believe that's why feature state unchanged), and I gave up
eventually. (If you have any idea to make it work, please guide me to the
light!!!)

Anyway, my main question is not about the above bug. For now, I am more
concerned about unable to remove the existing product, v1.0:
Case1: upgrade without upgrading MS Office (works)

When I tested the upgrade without upgrading MS Office, the upgrade works,
and there is only one entry (MyProduct v2.0) in Add/Remove Program (aka
ARP): the upgrade removed the earlier product entry from ARP.
Case2: upgrade after upgrading MS Office (disaster)

However, if I upgrade Office from Office 2003 to Office 2007 and then
perform the MSI upgrade, not only Word 2003 feature / Word 2007 feature
were installed, but also there are two entries (MyProduct v1.0 and
MyProduct v2.0) in ARP. If I tried to uninstall v1.0 in ARP, it seemed to
uninstall it, but if I refresh ARP, v1.0 re-appears, so I couldn't even
uninstall v1.0.

I compared the log files generated for both cases but it didn't tell me
why. And I have no idea why. Can anyone help me?
--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Bootstrapper logo in wrong location

2012-02-01 Thread Kyle Lee
Hi,

The WIX manual says,
"The WiX Standard Bootstrapper Application displays a generic logo in the
bottom left corner of the user interface."


I used this last year (the version was 3.6.1608.0), and yes, the log showed
up in the bottom left corner of the dialog.
Now I am using v3.6.2221.0 and it doesn't behave that way any more.
The logo is always in the top left corner and it only displays the square
shape, so that if my image is rectangle, it is clipped.

I strongly believe this is a regression.
If not, can anyone point me what I am missing?

TIA.
--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Custom Action for InstallExecuteSequence

2011-08-22 Thread Kyle Lee
I am trying to add some custom actions (CA's) after AppSearch.



However, since AppSearch action is in both InstallExecuteSequence and
InstallUISequence tables, my CA's are performed twice.

Is it possible to tell the installer to perform my CA's only during
InstallExecuteSequence, not during InstallUISequence?
--
uberSVN's rich system and user administration capabilities and model 
configuration take the hassle out of deploying and managing Subversion and 
the tools developers use with it. Learn more about uberSVN and get a free 
download at:  http://p.sf.net/sfu/wandisco-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Custom Action ignored during patch uninstall

2011-04-20 Thread Kyle Lee
Hi, I modified the custom actions from the original MSI so that during patch
install, those CAs can correct something that I missed in the original MSI.

The conditions I modified (I added "AND NOT PATCH AND NOT MSIPATCHREMOVE ")
are something like:



BEFORE (i.e. in the original MSI):

  IIS="IIS 6.0"



AFTER (i.e. in the newer MSI):

  IIS="IIS 6.0" AND NOT
PATCH AND NOT MSIPATCHREMOVE





And in patch WXS, I referred it to:







……



I want the same result for both patch-install and patch-uninstall.

When I installed this patch and looked at the logfile, I saw the condition
of "MyWebCA" was evaluated as FALSE, which is correct.

However, when I uninstalled the patch, that condition was evaluated as TRUE.



It seems during patch-uninstall, the original CA conditions were performed
by REINSTALL mode. Am I right?

How can I force both (patch-install and patch-uninstall) to evaluate the
newer condition???



FYI, the version of MSI on the machine I am testing is v3.
--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users