Re: [WiX-users] How to prevent the Publish* standardactionsfromshowing up.

2007-06-19 Thread Rob Mensching
I think suggesting NSIS is a requirement here is going a bit far.  There is 
something to be said for using the Windows Installer because it is still a 
declarative package.  However, it really isn't much different than a self 
extracting executable except that you can write a bunch more stuff.

Keep that in mind because people expect self-extracting exe's to not clean up 
after themselves (which isn't so bad since the exe's [usually] only dump files 
to a directory of choice).  MSI files on the other hand are supposed to be able 
to uninstall the stuff they litter all over the place (assuming they put stuff 
in ProgramMenuFolder, Registry, etc.).

Which leads to the question, Why use the Windows Installer?  Do self 
extracting technologies not let you display a dialog?

Finally, suggesting that something is okay because MSDN doesn't forbid it is a 
very slippery slope.  In fact, my interaction with the Windows Installer team 
tends to suggest that their documentation goes the other way.  If the MSI SDK 
doesn't say it is okay then you typically want to stay away from it.  For 
example, managed code CustomActions are the issue they hit me with all the time 
(the MSI SDK doesn't say you can use managed code for CustomActions so you 
shouldn't, as I've been told many times:  
http://robmensching.com/blog/archive/2007/04/19/Managed-Code-CustomActions-no-support-on-the-way-and-heres.aspx).

Anyway, what you're trying to do is a strange thing to do but as you've found 
in MSI SDK it says it's doable and Suppress=yes is the way the WiX toolset 
supports it.

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Leo ...
Sent: Monday, June 18, 2007 8:40 PM
To: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to prevent the Publish* standardactionsfromshowing 
up.


MSDN does not indicate any problems or recommand not doing this.  As a matter 
of fact MSDN provided the instruction for omitting the registration of 
application at http://msdn2.microsoft.com/en-us/library/aa367519.aspx  Exactly 
what kind issues I might get into if I do this.  Please advise.  Thx!


From: Mike Dimmick [EMAIL PROTECTED]
To: 'Leo ...' [EMAIL PROTECTED],wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to prevent the Publish* standardactionsfromshowing 
up.
Date: Mon, 18 Jun 2007 20:58:08 +0100
MIME-Version: 1.0
Received: from lists-outbound.sourceforge.net ([66.35.250.225]) by 
bay0-mc2-f1.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668); Mon, 18 Jun 
2007 12:58:16 -0700
Received: from sc8-sf-list1-new.sourceforge.net 
(sc8-sf-list1-new-b.sourceforge.net [10.3.1.93])by sc8-sf-spam2.sourceforge.net 
(Postfix) with ESMTPid A9A8AFAE9; Mon, 18 Jun 2007 12:58:15 -0700 (PDT)
Received: from sc8-sf-mx1-b.sourceforge.net 
([10.3.1.91]helo=mail.sourceforge.net)by sc8-sf-list1-new.sourceforge.net with 
esmtp (Exim 4.43)id 1I0NMa-0006VD-Utfor wix-users@lists.sourceforge.net; Mon, 
18 Jun 2007 12:58:13 -0700
Received: from anchor-post-33.mail.demon.net ([194.217.242.91])by 
mail.sourceforge.net with esmtp (Exim 4.44) id 1I0NMa-000503-2vfor 
wix-users@lists.sourceforge.net; Mon, 18 Jun 2007 12:58:12 -0700
Received: from dimmick.demon.co.uk ([83.104.49.50] helo=buzzard)by 
anchor-post-33.mail.demon.net with esmtp (Exim 4.42)id 1I0NMW-0007Wq-Af; Mon, 
18 Jun 2007 19:58:09 +
If you want a self-extracting ZIP file, use one. Don't abuse Windows Installer. 
It'll bite back.

Consider NSIS. http://nsis.sourceforge.net/Main_Page

--
Mike Dimmick


From: Leo ... [mailto:[EMAIL PROTECTED]
Sent: 18 June 2007 20:56
To: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to prevent the Publish* standard 
actionsfromshowing up.


What I want to do is creating a wrapper to display a dialog and then extract 
some files to disk.  Kind of like a self extracting zip file.  I don't want to 
make it a setup program where the user/admin needs to remove it.  Wouldn't 
removing these actions prevent the product from been registered as well as 
caching of the msi in the system therefore works the same as a self extracting 
zip file?


From: Mike Dimmick [EMAIL PROTECTED]
To: 'Leo ...' [EMAIL PROTECTED],wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to prevent the Publish* standard 
actionsfromshowing up.
Date: Mon, 18 Jun 2007 18:34:17 +0100
MIME-Version: 1.0
Received: from lists-outbound.sourceforge.net ([66.35.250.225]) by 
bay0-mc5-f7.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668); Mon, 18 Jun 
2007 10:34:42 -0700
Received: from sc8-sf-list1-new.sourceforge.net 
(sc8-sf-list1-new-b.sourceforge.net [10.3.1.93])by sc8-sf-spam2.sourceforge.net 
(Postfix) with ESMTPid 99A9E124DE; Mon, 18 Jun 2007 10:34:41 -0700 (PDT)
Received: from sc8-sf-mx2-b.sourceforge.net 
([10.3.1.92]helo=mail.sourceforge.net)by sc8-sf-list1-new.sourceforge.net with 
esmtp (Exim 4.43)id 1I0L7V

Re: [WiX-users] How to prevent the Publish* standardactionsfromshowing up.

2007-06-18 Thread Leo ...
MSDN does not indicate any problems or recommand not doing this. As a matter of fact MSDN provided theinstruction for omitting the registration of application at http://msdn2.microsoft.com/en-us/library/aa367519.aspx Exactly what kind issues I might get into if I do this. Please advise. Thx!


From: "Mike Dimmick" [EMAIL PROTECTED]To: "'Leo ...'" [EMAIL PROTECTED],wix-users@lists.sourceforge.netSubject: Re: [WiX-users] How to prevent the Publish* standardactionsfromshowing up.Date: Mon, 18 Jun 2007 20:58:08 +0100MIME-Version: 1.0Received: from lists-outbound.sourceforge.net ([66.35.250.225]) by bay0-mc2-f1.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668); Mon, 18 Jun 2007 12:58:16 -0700Received: from sc8-sf-list1-new.sourceforge.net (sc8-sf-list1-new-b.sourceforge.net [10.3.1.93])by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTPid A9A8AFAE9; Mon, 18 Jun 2007 12:58:15 -0700 (PDT)Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]helo=mail.sourceforge.net)by sc8-sf-list1-new.sourceforge.net with esmtp (Exim 4.43)id 1I0NMa-0006VD-Utfor 
wix-users@lists.sourceforge.net; Mon, 18 Jun 2007 12:58:13 -0700Received: from anchor-post-33.mail.demon.net ([194.217.242.91])by mail.sourceforge.net with esmtp (Exim 4.44) id 1I0NMa-000503-2vfor wix-users@lists.sourceforge.net; Mon, 18 Jun 2007 12:58:12 -0700Received: from dimmick.demon.co.uk ([83.104.49.50] helo=buzzard)by anchor-post-33.mail.demon.net with esmtp (Exim 4.42)id 1I0NMW-0007Wq-Af; Mon, 18 Jun 2007 19:58:09 +






If you want a self-extracting ZIP file, use one. Don’t abuse Windows Installer. It’ll bite back.

Consider NSIS. http://nsis.sourceforge.net/Main_Page

-- 
Mike Dimmick





From: Leo ... [mailto:[EMAIL PROTECTED] Sent: 18 June 2007 20:56To: [EMAIL PROTECTED]; wix-users@lists.sourceforge.netSubject: Re: [WiX-users] How to prevent the Publish* standard actionsfromshowing up.


What I want to do is creating a wrapper to display a dialog and then extract some files to disk. Kind of like a self extracting zip file. I don't want to make it a setup program where the user/admin needs to remove it. Wouldn't removing these actions preventthe product from been registered as well as caching of the msi in the system therefore works the same as a self extracting zip file?




From: "Mike Dimmick" [EMAIL PROTECTED]To: "'Leo ...'" [EMAIL PROTECTED],wix-users@lists.sourceforge.netSubject: Re: [WiX-users] How to prevent the Publish* standard actionsfromshowing up.Date: Mon, 18 Jun 2007 18:34:17 +0100MIME-Version: 1.0Received: from lists-outbound.sourceforge.net ([66.35.250.225]) by bay0-mc5-f7.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668); Mon, 18 Jun 2007 10:34:42 -0700Received: from sc8-sf-list1-new.sourceforge.net (sc8-sf-list1-new-b.sourceforge.net [10.3.1.93])by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTPid 99A9E124DE; Mon, 18 Jun 2007 10:34:41 -0700 (PDT)Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]helo=mail.sourceforge.net)by sc8-sf-list1-new.sourceforge.net with esmtp (Exim 4.43)id 1I0L7V-M4-ADfor wix-users@lists.sourceforge.net; Mon, 18 Jun 2007 10:34:29 -0700Received: from anchor-post-33.mail.demon.net ([194.217.242.91])by mail.sourceforge.net with esmtp (Exim 4.44) id 1I0L7T-0002dd-Msfor wix-users@lists.sourceforge.net; Mon, 18 Jun 2007 10:34:29 -0700Received: from dimmick.demon.co.uk ([83.104.49.50] helo=buzzard)by anchor-post-33.mail.demon.net with esmtp (Exim 4.42)id 1I0L7L-0002Rx-Cd; Mon, 18 Jun 2007 17:34:22 +
 
You can suppress a standard action in WiX by using e.g. PublishFeatures/@Suppress=’yes’.

I’m guessing you’re trying to prevent the end-user from uninstalling your package. Don’t do this. It’s the user’s machine, not yours. If, as a network administrator, you want to stop your users uninstalling software, it’s simple: make them a standard user.

If you really want to hide the component from Add/Remove Programs, set the ARPSYSTEMCOMPONENT property to 1. Again, it’s the user’s computer, not yours.

-- 
Mike Dimmick





From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Leo ...Sent: 18 June 2007 03:59To: wix-users@lists.sourceforge.netSubject: [WiX-users] How to prevent the Publish* standard actions fromshowing up.



How do you define the InstallExecuteSequence table in WIX so that the standard actions PublishFeatures, PublishProduct, RegisterProduct and RegisterUserswon'tshow up? thx!

-This SF.net email is sponsored by DB2 ExpressDownload DB2 Express C - the FREE version of DB2 express and takecontrol of your XML. No limits. Just data. Click to get it now.http://sourceforge.net/powerbar/db2/
___WiX-users mailing listWiX-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wix-users
-This SF.net email is sponsored by DB2 ExpressDownload DB2 Express C - the FREE version of DB2