Re: [WiX-users] How to get the SourceDir in a MSI package that is bundled within burn?
Hm... no answer yet? Are my questions not understandable or too strange? ;-)
Ok, as perhaps some users might be interested in a solution, I present the way
I have chosen for now:
Basic Idea is to simply write a small C# Program, that gets the Path from a wix
burn bundle via CLI, shortens it by removing the ``setup.exe``-part and write
the result (the plain source path) into a defined registry key. Other
components of an installer bundle can retrieve this key and use the information
for further setup process.
The Mini-Program look like this:
namespace RegisterPath
{
class Program
{
static void Main(string[] args)
{
Registry.SetValue(string.Format(@{0}\{1},
RegisterPath.Properties.Resources.root, RegisterPath.Properties.Resources.key),
RegisterPath.Properties.Resources.valuename,
Path.GetDirectoryName(args[0]));
}
}
}
As you can see I use resource-strings for the definition of the registry key.
The fragment within the burn bundle to call the programm:
Fragment
PackageGroup Id=RegisterPath
ExePackage Name=RegisterPath.exe Id=RegisterPath_PK
SourceFile=$(var.RegisterPathPath)
InstallCommand='[WixBundleOriginalSource]'
Cache=no Compressed=yes PerMachine=yes Vital=yes/
/PackageGroup
/Fragment
As you can see I use the ``WixBundleOriginalSource``-variable provided from
burn (Which is the heart of the problem ;-) ).
Further down in my bundle package I refer to this in order to provide the path
to a Msi-Package:
Fragment
util:RegistrySearch Id=BasePathSearch
Variable=BASEPATHPROP
Root=HKCU
Key=Software\$(var.Manufacturer)
Result=value
Value=BasePath /
PackageGroup Id=ClientMsi
MsiPackage SourceFile=$(var.ClientMSIPath)
MsiProperty Name=MYBASEPATH Value=[BASEPATHPROP]\/
/MsiPackage
/PackageGroup
/Fragment
One must take care that the Properties of the C#-Program and the attributes of
the RegistrySearch within the wix bundle are equal. Normally that does not
change too often, so I can live with that workaround for the moment.
Of course I would appreciate a more elegant solution; the best would be a
predefined variable by burn itself ;-)
Best regards,
-Ursprüngliche Nachricht-
Von: Christian Hausknecht [mailto:chauskne...@beracom.de]
Gesendet: Montag, 27. August 2012 13:00
An: General discussion for Windows Installer XML toolset.
Betreff: Re: [WiX-users] How to get the SourceDir in a MSI package that is
bundled within burn?
Ok, I kept thinking about the problem and I have an idea, that probably could
lead to the right direction.
I can define a msi-property within the bundle definition to that one must
assign the current path and that can be used within the MSI package definition
as reference. I tried the following approach:
!-- Define MsiProperty within the burn bundle file -- MsiPackage
SourceFile=$(var.ClientMSIPath)
MsiProperty Name=MYSOURCEDIR Value=[WixBundleOriginalSource]\/
/MsiPackage
!-- Reference the property within the MSI definition -- Shortcut
Id=Foo_ShortCut
Name=Foo
Description=Foo
Target=[MYSOURCEDIR]Foo.exe
WorkingDirectory=ProgramFilesFolder/
That would work fine besides the wix variable `` WixBundleOriginalSource``
holds not only the path of the starting dir but the complete path *including*
the exe-filename :-( Is there any way to trim the value or maybe another
burn-variable, that holds only the path?
-Ursprüngliche Nachricht-
Von: Christian Hausknecht [mailto:chauskne...@beracom.de]
Gesendet: Montag, 27. August 2012 11:04
An: wix-users@lists.sourceforge.net
Betreff: [WiX-users] How to get the SourceDir in a MSI package that is bundled
within burn?
Hello folks,
I have basically the same question as the guy here:
http://stackoverflow.com/questions/10573135/wix-installer-how-can-i-get-setup-exes-current-directory
I have created a MSI where some Shortcuts for the Menu and the Desktop are
created. They are created for applications, which are already installed and
therefore are not part of my installation routine. The installer itself is
located in the same directory. If I just test the MSI, then
``Target=[SourceDir]Foo.exe`` just works as expected. But when I embedd this
MSI into a bundle built with burn, then [SourceDir] does not refer to the
Directory, where the Installer is located. Instead it refers to
%TEMP%\{ProductID}\{Version}\Foo.exe. But I do not need this path but the one
I get if I install the MSI directly.
As the Path is variable, I *must* be able to refer to the actual starting
directory of the installer.exe. Can anyone provide a solution for that?
Greetings,
Mit freundlichen Grüßen
Christian Hausknecht
Entwicklung
BeraCom
Beratung und Software-Entwicklung GmbH Co. KG
Re: [WiX-users] About Commercial Use
There is no fee for using wix to produce your own installers. See http://robmensching.com/blog/posts/2012/8/20/The-WiX-toolset-license -Original Message- From: ?? ?? [mailto:satoshi.mizuko...@jp.advantest.com] Sent: 27 August 2012 10:34 To: wix-users@lists.sourceforge.net Subject: [WiX-users] About Commercial Use Hi All, I'd like to adopt WiX to make an installer including my company's product without a fee. I confirm whether WiX needs to be paid nothing for commercial use really. (whether I don't have to register anything with Microsoft) Can any answer please. Regards, Satoshi -- S.Mizukoshi Email:satoshi.mizuko...@jp.advantest.com - - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Read a property
Hi, Is there any way to do this? I have a Custom Action that's sets the property: Property Id=PRODUCTNAME Secure=yes / That's 100%, But now I would like to read that property value as it can be a few different outcomes and if it is outcome 1 then I would like to run a second custom action. (e.g PRODUCTNAME = 'Coral') Can this be done in wix? I was thinking it was maybe possible using conditions but I am not too sure how I would go about it. Kind Regards, Natalie Carr -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] About Commercial Use
Thanks Peter, I can adopt WiX without anxiety.:) (2012/08/28 19:34), Peter Shirtcliffe wrote: There is no fee for using wix to produce your own installers. See http://robmensching.com/blog/posts/2012/8/20/The-WiX-toolset-license -Original Message- From: ?? ?? [mailto:satoshi.mizuko...@jp.advantest.com] Sent: 27 August 2012 10:34 To: wix-users@lists.sourceforge.net Subject: [WiX-users] About Commercial Use Hi All, I'd like to adopt WiX to make an installer including my company's product without a fee. I confirm whether WiX needs to be paid nothing for commercial use really. (whether I don't have to register anything with Microsoft) Can any answer please. Regards, Satoshi -- S.Mizukoshi Email:satoshi.mizuko...@jp.advantest.com - - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Read a property
Custom actions can have conditions, which can be based on property values http://wix.tramontana.co.hu/tutorial/events-and-actions/extra-actions In UI or execute sequence Custom Actrion=doIt...PRODUCTNAME=Coral/Custom -Original Message- From: Natalie Carr [mailto:natalie.c...@measuresoft.com] Sent: 28 August 2012 11:40 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Read a property Hi, Is there any way to do this? I have a Custom Action that's sets the property: Property Id=PRODUCTNAME Secure=yes / That's 100%, But now I would like to read that property value as it can be a few different outcomes and if it is outcome 1 then I would like to run a second custom action. (e.g PRODUCTNAME = 'Coral') Can this be done in wix? I was thinking it was maybe possible using conditions but I am not too sure how I would go about it. Kind Regards, Natalie Carr - - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Read a property
Thank you so much, knew it would have been something simple..:) -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: 28 August 2012 12:07 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Read a property Custom actions can have conditions, which can be based on property values http://wix.tramontana.co.hu/tutorial/events-and-actions/extra-actions In UI or execute sequence Custom Actrion=doIt...PRODUCTNAME=Coral/Custom -Original Message- From: Natalie Carr [mailto:natalie.c...@measuresoft.com] Sent: 28 August 2012 11:40 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Read a property Hi, Is there any way to do this? I have a Custom Action that's sets the property: Property Id=PRODUCTNAME Secure=yes / That's 100%, But now I would like to read that property value as it can be a few different outcomes and if it is outcome 1 then I would like to run a second custom action. (e.g PRODUCTNAME = 'Coral') Can this be done in wix? I was thinking it was maybe possible using conditions but I am not too sure how I would go about it. Kind Regards, Natalie Carr - - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Windows 8 NetFX3.5
I have an installation which has the .NET Framework 3.5 etc. as prerequisites. In the past I've been able to install the .NET Framework by calling the redistributable package. What is the correct approach for Windows 8? Most of my target market does not have internet connectivity. IT departments install machines then pass them out to the users. There are no ISO images of the Windows 8 install or folders that I'm aware of on users machines that enable me to call dism /online /enable-feature /featurename:NetFx3 /all /source:Win8Source\sources\sxs as the source is held with the IT departments. Should I just fail the install as I can't install the prerequisite? Or have I got the wrong approach. Neil -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Windows 8 NetFX3.5
The approach I am using is to run ocsetup NetFx3, this seems to work ok and does not require internet access. Neil -Original Message- From: Neil Hayes [mailto:neil.ha...@syspro.com] Sent: 28 August 2012 1:24 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Windows 8 NetFX3.5 I have an installation which has the .NET Framework 3.5 etc. as prerequisites. In the past I've been able to install the .NET Framework by calling the redistributable package. What is the correct approach for Windows 8? Most of my target market does not have internet connectivity. IT departments install machines then pass them out to the users. There are no ISO images of the Windows 8 install or folders that I'm aware of on users machines that enable me to call dism /online /enable-feature /featurename:NetFx3 /all /source:Win8Source\sources\sxs as the source is held with the IT departments. Should I just fail the install as I can't install the prerequisite? Or have I got the wrong approach. Neil -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Managed Custom Action using CAS
Hi, I have upgraded an old installer to a wix 3.7 custom action project that uses the old CAS policy methods. I've upgraded the solution to runtime 4 and resulted receiving the exception This method explicitly uses CAS policy, which has been obsoleted by the .NET Framework. // Get the policy level. PolicyLevel policyLevel = CustomAction.GetPolicyLevel(SomePolicyLabel); In order to enable CAS policy for compatibility reasons, please use the NetFx40_LegacySecurityPolicy configuration switch. Please see http://go.microsoft.com/fwlink/?LinkID=155570 for more information. Following the link I ended up specifying in the CustomAction.config file to use the legacy CAS method overloads. ?xml version=1.0 encoding=utf-8 ? configuration startup useLegacyV2RuntimeActivationPolicy=true supportedRuntime version=v4.0 sku=.NETFramework,Version=v4.0/ supportedRuntime version=v2.0.50727/ /startup runtime NetFx40_LegacySecurityPolicy enabled=true/ /runtime /configuration I've tried a bunch of things to resolve the issue but with no luck. Any ideas anyone? Thanks in advanced. Kind regards, Christoffel le Roux -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Managed Custom Action using CAS
I guess the real question would be do you even need this in .Net 4? http://blogs.msdn.com/b/shawnfa/archive/2010/02/24/so-is-cas-dead-in-net-4-or-what.aspx What is the custom action trying to accomplish with CAS? -Original Message- From: Christoffel le Roux [mailto:christoffe...@tech.flowcentric.com] Sent: Tuesday, August 28, 2012 9:12 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Managed Custom Action using CAS Hi, I have upgraded an old installer to a wix 3.7 custom action project that uses the old CAS policy methods. I've upgraded the solution to runtime 4 and resulted receiving the exception This method explicitly uses CAS policy, which has been obsoleted by the .NET Framework. // Get the policy level. PolicyLevel policyLevel = CustomAction.GetPolicyLevel(SomePolicyLabel); In order to enable CAS policy for compatibility reasons, please use the NetFx40_LegacySecurityPolicy configuration switch. Please see http://go.microsoft.com/fwlink/?LinkID=155570 for more information. Following the link I ended up specifying in the CustomAction.config file to use the legacy CAS method overloads. ?xml version=1.0 encoding=utf-8 ? configuration startup useLegacyV2RuntimeActivationPolicy=true supportedRuntime version=v4.0 sku=.NETFramework,Version=v4.0/ supportedRuntime version=v2.0.50727/ /startup runtime NetFx40_LegacySecurityPolicy enabled=true/ /runtime /configuration I've tried a bunch of things to resolve the issue but with no luck. Any ideas anyone? Thanks in advanced. Kind regards, Christoffel le Roux -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Managed Custom Action using CAS
Hi Jacob, Thanks for the reply, I'm installing an office 2003 VSTO project and using the custom action which in turn needs the CAS policy methods to register the DLL as safe to be consumed by Office. Kind regards, Christoffel le Roux -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Tuesday, August 28, 2012 4:22 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Managed Custom Action using CAS I guess the real question would be do you even need this in .Net 4? http://blogs.msdn.com/b/shawnfa/archive/2010/02/24/so-is-cas-dead-in-net-4-or-what.aspx What is the custom action trying to accomplish with CAS? -Original Message- From: Christoffel le Roux [mailto:christoffe...@tech.flowcentric.com] Sent: Tuesday, August 28, 2012 9:12 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Managed Custom Action using CAS Hi, I have upgraded an old installer to a wix 3.7 custom action project that uses the old CAS policy methods. I've upgraded the solution to runtime 4 and resulted receiving the exception This method explicitly uses CAS policy, which has been obsoleted by the .NET Framework. // Get the policy level. PolicyLevel policyLevel = CustomAction.GetPolicyLevel(SomePolicyLabel); In order to enable CAS policy for compatibility reasons, please use the NetFx40_LegacySecurityPolicy configuration switch. Please see http://go.microsoft.com/fwlink/?LinkID=155570 for more information. Following the link I ended up specifying in the CustomAction.config file to use the legacy CAS method overloads. ?xml version=1.0 encoding=utf-8 ? configuration startup useLegacyV2RuntimeActivationPolicy=true supportedRuntime version=v4.0 sku=.NETFramework,Version=v4.0/ supportedRuntime version=v2.0.50727/ /startup runtime NetFx40_LegacySecurityPolicy enabled=true/ /runtime /configuration I've tried a bunch of things to resolve the issue but with no luck. Any ideas anyone? Thanks in advanced. Kind regards, Christoffel le Roux -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Assistance with Burn
I really could use some assistance with this. I have changed WixStandardBootstrapperApplication.cpp as I mentioned, but I can't figure out what to build (do I build at the ext source level or where), how to build it (I get lots of errors and warnings that files are missing when I try to open ext.sln). Can someone explain where, what, and how I need to build? I have made a dll in the wixstdba directory, but I don't know how to use the dll within the burn bundle. I attempted to make the BootsrapperApplication in my wxs file, but of course that did not work. Any ideas on what I need to do? -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: Friday, August 24, 2012 2:12 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Assistance with Burn I have been attempting to make simple changes to the theme of my burn application. Most of this has been easy, but I am now running into a few things that I can't seem to find simple answers to. First, if the user cancels the install from my bootstrap, it shows that the install failed and gives the error code and description (as provided in the examples). Without creating my own BA, is there a way to have conditional text for User canceled vs a real error? Also, how do I turn on the error logs for Burn (and where does it put them by default - I am new to all this and I don't really know where %temp% is). Second, if I have to create my own BA to handle this, how do I go about integrating it into my bootstrap? I have made changes to WixStandardBootstrapperApplication.cpp, but I don't know what to do with the dll generated or how and where to put the config file (I have seen examples of some of this but there is no concise information on what to do and where to put it). -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Conditional Uninstall - Need to workaround WiX Certificate custom action bugs
We have a product that installs a few certificates on the system using the IIS extension using WiX 3.0. Evidently, there is an issue with the certificate action(s) in this version of the toolset. We are unable to uninstall/upgrade from this specific version in the field. I would like to know if there is a way during the uninstall (i.e. msiexec /x .) to pass command line parameters/properties to skip the uninstall of specific components, in this case the certificate that is giving us problems. The original authoring has conditions to skip the certificates when installing the product. Passing these properties during the uninstall does not seem to skip them during the uninstall process (like I was hoping it would). Ultimately, we have tested with WiX 3.5 and the bug appears to be fixed. So, we would like to be able to get the old version of the product uninstalled, leaving the certificate it originally installed behind, and then with the new WiX 3.5-built package reinstall the certificate hoping to workaround this original WiX 3.0 issue. If there is no other way to selectively uninstall, is there a possible way of forcibly causing the uninstall to succeed (understanding that some artifacts might be left behind)? I have all of the details of the original installation package, so if anything can be done I would very much appreciate the help. Thanks. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditional Uninstall - Need to workaround WiX Certificate custom action bugs
As far as I can think, you can only selectively uninstall entire features without using permanent components. If the conditions are broken, would patching/minor updating them solve your problem ? I'm not sure what the WiX bug is that you're referring to. Otherwise, you could write an extra installer that only includes the component you want to keep, install that, then remove the original one. The extra reference would retain the component on the machine until you took both installers off. -Original Message- From: Andy Clugston [mailto:clug...@gmail.com] Sent: 28 August 2012 16:15 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Conditional Uninstall - Need to workaround WiX Certificate custom action bugs We have a product that installs a few certificates on the system using the IIS extension using WiX 3.0. Evidently, there is an issue with the certificate action(s) in this version of the toolset. We are unable to uninstall/upgrade from this specific version in the field. I would like to know if there is a way during the uninstall (i.e. msiexec /x .) to pass command line parameters/properties to skip the uninstall of specific components, in this case the certificate that is giving us problems. The original authoring has conditions to skip the certificates when installing the product. Passing these properties during the uninstall does not seem to skip them during the uninstall process (like I was hoping it would). Ultimately, we have tested with WiX 3.5 and the bug appears to be fixed. So, we would like to be able to get the old version of the product uninstalled, leaving the certificate it originally installed behind, and then with the new WiX 3.5-built package reinstall the certificate hoping to workaround this original WiX 3.0 issue. If there is no other way to selectively uninstall, is there a possible way of forcibly causing the uninstall to succeed (understanding that some artifacts might be left behind)? I have all of the details of the original installation package, so if anything can be done I would very much appreciate the help. Thanks. - - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditional Uninstall - Need to workaround WiX Certificate custom action bugs
Okay, so what you are saying is that I cannot skip individual components during uninstall, correct? I am not sure if these would work or not. We don't have minor installs, we use the third digit, but it is a full install. This product installs the certificate, and another product re-installs the identical certificate. For some reason WiX 3.0 does not like this. I would have to dig up the bug report, but I did run across it. During our tests with WiX 3.5 this issue seems to be resolved. Now, we could get into a conversation about cross product dependencies, etc. but I was not involved with any of those decisions so I am just trying to dig us out of the hole we are in. I am not sure the extra installer is going to help. It appears that anything touching the original certificate on the system causes the original WiX 3.0 MSI to fail. Yes, the install would ensure the cert is on the system, but the uninstall for the original WiX 3.0 MSI package would still fail. Thanks for the help. On Tue, Aug 28, 2012 at 11:46 AM, Peter Shirtcliffe pshirtcli...@sdl.comwrote: As far as I can think, you can only selectively uninstall entire features without using permanent components. If the conditions are broken, would patching/minor updating them solve your problem ? I'm not sure what the WiX bug is that you're referring to. Otherwise, you could write an extra installer that only includes the component you want to keep, install that, then remove the original one. The extra reference would retain the component on the machine until you took both installers off. -Original Message- From: Andy Clugston [mailto:clug...@gmail.com] Sent: 28 August 2012 16:15 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Conditional Uninstall - Need to workaround WiX Certificate custom action bugs We have a product that installs a few certificates on the system using the IIS extension using WiX 3.0. Evidently, there is an issue with the certificate action(s) in this version of the toolset. We are unable to uninstall/upgrade from this specific version in the field. I would like to know if there is a way during the uninstall (i.e. msiexec /x .) to pass command line parameters/properties to skip the uninstall of specific components, in this case the certificate that is giving us problems. The original authoring has conditions to skip the certificates when installing the product. Passing these properties during the uninstall does not seem to skip them during the uninstall process (like I was hoping it would). Ultimately, we have tested with WiX 3.5 and the bug appears to be fixed. So, we would like to be able to get the old version of the product uninstalled, leaving the certificate it originally installed behind, and then with the new WiX 3.5-built package reinstall the certificate hoping to workaround this original WiX 3.0 issue. If there is no other way to selectively uninstall, is there a possible way of forcibly causing the uninstall to succeed (understanding that some artifacts might be left behind)? I have all of the details of the original installation package, so if anything can be done I would very much appreciate the help. Thanks. - - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat
Re: [WiX-users] Conditional Uninstall - Need to workaround WiX Certificate custom action bugs
Correct. Having thought about it a bit more, this might be a better idea: Take the original installer (or whatever is the current release). Make a major upgrade out of it in the normal way. Schedule RemoveExistingProducts in one of the latter two places mentioned in http://msdn.microsoft.com/en-us/library/windows/desktop/aa371197%28v=vs.85%29 .aspx Build it with WiX 3.5 That'll create a major upgrade that shouldn't touch the certificate component. Being built with WiX 3.5, removal might then succeed. I'm not sure what the WiX team would say about mixing toolset versions like that but I'd guess there are risks, so you'd have to test thoroughly. You'd have to do the same thing with the second product too since you don't know which one will be removed last and will perform the actual certificate uninstallation. -Original Message- From: Andy Clugston [mailto:clug...@gmail.com] Sent: 28 August 2012 17:20 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional Uninstall - Need to workaround WiX Certificate custom action bugs Okay, so what you are saying is that I cannot skip individual components during uninstall, correct? I am not sure if these would work or not. We don't have minor installs, we use the third digit, but it is a full install. This product installs the certificate, and another product re-installs the identical certificate. For some reason WiX 3.0 does not like this. I would have to dig up the bug report, but I did run across it. During our tests with WiX 3.5 this issue seems to be resolved. Now, we could get into a conversation about cross product dependencies, etc. but I was not involved with any of those decisions so I am just trying to dig us out of the hole we are in. I am not sure the extra installer is going to help. It appears that anything touching the original certificate on the system causes the original WiX 3.0 MSI to fail. Yes, the install would ensure the cert is on the system, but the uninstall for the original WiX 3.0 MSI package would still fail. Thanks for the help. On Tue, Aug 28, 2012 at 11:46 AM, Peter Shirtcliffe pshirtcli...@sdl.comwrote: As far as I can think, you can only selectively uninstall entire features without using permanent components. If the conditions are broken, would patching/minor updating them solve your problem ? I'm not sure what the WiX bug is that you're referring to. Otherwise, you could write an extra installer that only includes the component you want to keep, install that, then remove the original one. The extra reference would retain the component on the machine until you took both installers off. -Original Message- From: Andy Clugston [mailto:clug...@gmail.com] Sent: 28 August 2012 16:15 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Conditional Uninstall - Need to workaround WiX Certificate custom action bugs We have a product that installs a few certificates on the system using the IIS extension using WiX 3.0. Evidently, there is an issue with the certificate action(s) in this version of the toolset. We are unable to uninstall/upgrade from this specific version in the field. I would like to know if there is a way during the uninstall (i.e. msiexec /x .) to pass command line parameters/properties to skip the uninstall of specific components, in this case the certificate that is giving us problems. The original authoring has conditions to skip the certificates when installing the product. Passing these properties during the uninstall does not seem to skip them during the uninstall process (like I was hoping it would). Ultimately, we have tested with WiX 3.5 and the bug appears to be fixed. So, we would like to be able to get the old version of the product uninstalled, leaving the certificate it originally installed behind, and then with the new WiX 3.5-built package reinstall the certificate hoping to workaround this original WiX 3.0 issue. If there is no other way to selectively uninstall, is there a possible way of forcibly causing the uninstall to succeed (understanding that some artifacts might be left behind)? I have all of the details of the original installation package, so if anything can be done I would very much appreciate the help. Thanks. -- --- - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the
Re: [WiX-users] Managed Custom Action using CAS
I've never done one of those myself, but a bit of search engine foo shows a few potential links http://social.msdn.microsoft.com/Forums/eu/vsto/thread/f46b54a0-0fc3-4a76-a47c-aad05e31bb86 , http://social.msdn.microsoft.com/Forums/en/vsto/thread/890cb60c-11f6-4fea-8a44-e520341f3331 , and http://stackoverflow.com/questions/3089567/is-it-possible-to-create-an-office-2003-vsto-add-in-from-visual-studio-2010 . From the second link I find: Different Visual Studio Versions 1. Visual Studio 2010 supports creating VSTO 3.0 and VSTO 4.0 solutions. 2. Visual Studio 2008 supports creating VSTO 2.0 and VSTO 3.0 solutions. - Different VSTO Versions 1. VSTO 2.0 solutions work with Office 2003 and Office 2007 2. VSTO 3.0 solutions work with Office 2007 and Office 2010 - Since you stated you needed an Office 2003 VSTO, I don't think it would be possible to have it using the 4.0 framework (for the addin). As such, what benefit are you getting by upgrading the CA DLL? If you need the old behavior and a new feature then you could have 2 CA DLL's; one targeting 4.0 for the new stuff and one targeting 2.0 for the old CAS calls. If you want to continue to try to get 4.0 to work, then the actual framework call that is failing (the source to CustomAction.GetPolicyLevel ) would be helpful. -Original Message- From: Christoffel le Roux [mailto:christoffe...@tech.flowcentric.com] Sent: Tuesday, August 28, 2012 9:33 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Managed Custom Action using CAS Hi Jacob, Thanks for the reply, I'm installing an office 2003 VSTO project and using the custom action which in turn needs the CAS policy methods to register the DLL as safe to be consumed by Office. Kind regards, Christoffel le Roux -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Tuesday, August 28, 2012 4:22 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Managed Custom Action using CAS I guess the real question would be do you even need this in .Net 4? http://blogs.msdn.com/b/shawnfa/archive/2010/02/24/so-is-cas-dead-in-net-4-or-what.aspx What is the custom action trying to accomplish with CAS? -Original Message- From: Christoffel le Roux [mailto:christoffe...@tech.flowcentric.com] Sent: Tuesday, August 28, 2012 9:12 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Managed Custom Action using CAS Hi, I have upgraded an old installer to a wix 3.7 custom action project that uses the old CAS policy methods. I've upgraded the solution to runtime 4 and resulted receiving the exception This method explicitly uses CAS policy, which has been obsoleted by the .NET Framework. // Get the policy level. PolicyLevel policyLevel = CustomAction.GetPolicyLevel(SomePolicyLabel); In order to enable CAS policy for compatibility reasons, please use the NetFx40_LegacySecurityPolicy configuration switch. Please see http://go.microsoft.com/fwlink/?LinkID=155570 for more information. Following the link I ended up specifying in the CustomAction.config file to use the legacy CAS method overloads. ?xml version=1.0 encoding=utf-8 ? configuration startup useLegacyV2RuntimeActivationPolicy=true supportedRuntime version=v4.0 sku=.NETFramework,Version=v4.0/ supportedRuntime version=v2.0.50727/ /startup runtime NetFx40_LegacySecurityPolicy enabled=true/ /runtime /configuration I've tried a bunch of things to resolve the issue but with no luck. Any ideas anyone? Thanks in advanced. Kind regards, Christoffel le Roux -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive
Re: [WiX-users] Conditional Uninstall - Need to workaround WiX Certificate custom action bugs
I assume when you say take the original installer you mean bump one of the three version digits and generate a new product version installer, i.e. 1.1.0 to 1.1.1, generate new product GUID, etc. Where this all started was trying to get a newer version of the product on the system. If I can make the RemoveExistingProducts changes to it and that actually works, then we should not need to figure out how to uninstall it first. On Tue, Aug 28, 2012 at 12:42 PM, Peter Shirtcliffe pshirtcli...@sdl.comwrote: Correct. Having thought about it a bit more, this might be a better idea: Take the original installer (or whatever is the current release). Make a major upgrade out of it in the normal way. Schedule RemoveExistingProducts in one of the latter two places mentioned in http://msdn.microsoft.com/en-us/library/windows/desktop/aa371197%28v=vs.85%29 .aspx Build it with WiX 3.5 That'll create a major upgrade that shouldn't touch the certificate component. Being built with WiX 3.5, removal might then succeed. I'm not sure what the WiX team would say about mixing toolset versions like that but I'd guess there are risks, so you'd have to test thoroughly. You'd have to do the same thing with the second product too since you don't know which one will be removed last and will perform the actual certificate uninstallation. -Original Message- From: Andy Clugston [mailto:clug...@gmail.com] Sent: 28 August 2012 17:20 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional Uninstall - Need to workaround WiX Certificate custom action bugs Okay, so what you are saying is that I cannot skip individual components during uninstall, correct? I am not sure if these would work or not. We don't have minor installs, we use the third digit, but it is a full install. This product installs the certificate, and another product re-installs the identical certificate. For some reason WiX 3.0 does not like this. I would have to dig up the bug report, but I did run across it. During our tests with WiX 3.5 this issue seems to be resolved. Now, we could get into a conversation about cross product dependencies, etc. but I was not involved with any of those decisions so I am just trying to dig us out of the hole we are in. I am not sure the extra installer is going to help. It appears that anything touching the original certificate on the system causes the original WiX 3.0 MSI to fail. Yes, the install would ensure the cert is on the system, but the uninstall for the original WiX 3.0 MSI package would still fail. Thanks for the help. On Tue, Aug 28, 2012 at 11:46 AM, Peter Shirtcliffe pshirtcli...@sdl.comwrote: As far as I can think, you can only selectively uninstall entire features without using permanent components. If the conditions are broken, would patching/minor updating them solve your problem ? I'm not sure what the WiX bug is that you're referring to. Otherwise, you could write an extra installer that only includes the component you want to keep, install that, then remove the original one. The extra reference would retain the component on the machine until you took both installers off. -Original Message- From: Andy Clugston [mailto:clug...@gmail.com] Sent: 28 August 2012 16:15 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Conditional Uninstall - Need to workaround WiX Certificate custom action bugs We have a product that installs a few certificates on the system using the IIS extension using WiX 3.0. Evidently, there is an issue with the certificate action(s) in this version of the toolset. We are unable to uninstall/upgrade from this specific version in the field. I would like to know if there is a way during the uninstall (i.e. msiexec /x .) to pass command line parameters/properties to skip the uninstall of specific components, in this case the certificate that is giving us problems. The original authoring has conditions to skip the certificates when installing the product. Passing these properties during the uninstall does not seem to skip them during the uninstall process (like I was hoping it would). Ultimately, we have tested with WiX 3.5 and the bug appears to be fixed. So, we would like to be able to get the old version of the product uninstalled, leaving the certificate it originally installed behind, and then with the new WiX 3.5-built package reinstall the certificate hoping to workaround this original WiX 3.0 issue. If there is no other way to selectively uninstall, is there a possible way of forcibly causing the uninstall to succeed (understanding that some artifacts might be left behind)? I have all of the details of the original installation package, so if anything can be done I would very much appreciate the help. Thanks.
[WiX-users] Install Wix37.exe using command line.
Hello all, We had a build machine which used to install Wix3.6 msi using msiexec /qr /i WiX\wix36.msi Now, we are updating our build scripts to use Wix37.exe , but I dont know is there a way to install latest wix using command line ? Are there any options with this exe so that i can silent install wix37.exe on command line ? Thanks Vivek -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Install-Wix37-exe-using-command-line-tp7580153.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Overriable variable are case sensitve.
Commandline parameters are case sensitive when setting up overriable variables and passing them to an MSI using the stdba. Is there a way around this? i.e. How to we recognize command line parameters coming in where case doesn't match? Thanks. Darwin -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditional Uninstall - Need to workaround WiX Certificate custom action bugs
So I created a new version (major upgrade) of the product. I adjusted RemoveExistingProducts to run after InstallFinalize. This didn't seem to help at all. It still attempts to remove the cert, and I have the same errors. Thanks. On Tue, Aug 28, 2012 at 3:26 PM, Andy Clugston clug...@gmail.com wrote: I assume when you say take the original installer you mean bump one of the three version digits and generate a new product version installer, i.e. 1.1.0 to 1.1.1, generate new product GUID, etc. Where this all started was trying to get a newer version of the product on the system. If I can make the RemoveExistingProducts changes to it and that actually works, then we should not need to figure out how to uninstall it first. On Tue, Aug 28, 2012 at 12:42 PM, Peter Shirtcliffe pshirtcli...@sdl.comwrote: Correct. Having thought about it a bit more, this might be a better idea: Take the original installer (or whatever is the current release). Make a major upgrade out of it in the normal way. Schedule RemoveExistingProducts in one of the latter two places mentioned in http://msdn.microsoft.com/en-us/library/windows/desktop/aa371197%28v=vs.85%29 .aspx Build it with WiX 3.5 That'll create a major upgrade that shouldn't touch the certificate component. Being built with WiX 3.5, removal might then succeed. I'm not sure what the WiX team would say about mixing toolset versions like that but I'd guess there are risks, so you'd have to test thoroughly. You'd have to do the same thing with the second product too since you don't know which one will be removed last and will perform the actual certificate uninstallation. -Original Message- From: Andy Clugston [mailto:clug...@gmail.com] Sent: 28 August 2012 17:20 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Conditional Uninstall - Need to workaround WiX Certificate custom action bugs Okay, so what you are saying is that I cannot skip individual components during uninstall, correct? I am not sure if these would work or not. We don't have minor installs, we use the third digit, but it is a full install. This product installs the certificate, and another product re-installs the identical certificate. For some reason WiX 3.0 does not like this. I would have to dig up the bug report, but I did run across it. During our tests with WiX 3.5 this issue seems to be resolved. Now, we could get into a conversation about cross product dependencies, etc. but I was not involved with any of those decisions so I am just trying to dig us out of the hole we are in. I am not sure the extra installer is going to help. It appears that anything touching the original certificate on the system causes the original WiX 3.0 MSI to fail. Yes, the install would ensure the cert is on the system, but the uninstall for the original WiX 3.0 MSI package would still fail. Thanks for the help. On Tue, Aug 28, 2012 at 11:46 AM, Peter Shirtcliffe pshirtcli...@sdl.comwrote: As far as I can think, you can only selectively uninstall entire features without using permanent components. If the conditions are broken, would patching/minor updating them solve your problem ? I'm not sure what the WiX bug is that you're referring to. Otherwise, you could write an extra installer that only includes the component you want to keep, install that, then remove the original one. The extra reference would retain the component on the machine until you took both installers off. -Original Message- From: Andy Clugston [mailto:clug...@gmail.com] Sent: 28 August 2012 16:15 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Conditional Uninstall - Need to workaround WiX Certificate custom action bugs We have a product that installs a few certificates on the system using the IIS extension using WiX 3.0. Evidently, there is an issue with the certificate action(s) in this version of the toolset. We are unable to uninstall/upgrade from this specific version in the field. I would like to know if there is a way during the uninstall (i.e. msiexec /x .) to pass command line parameters/properties to skip the uninstall of specific components, in this case the certificate that is giving us problems. The original authoring has conditions to skip the certificates when installing the product. Passing these properties during the uninstall does not seem to skip them during the uninstall process (like I was hoping it would). Ultimately, we have tested with WiX 3.5 and the bug appears to be fixed. So, we would like to be able to get the old version of the product uninstalled, leaving the certificate it originally installed behind, and then with the new WiX 3.5-built package reinstall the certificate hoping to workaround this original WiX 3.0 issue. If there is no other way to selectively uninstall, is there a
Re: [WiX-users] Install Wix37.exe using command line.
wix37.exe -quiet On Tue, Aug 28, 2012 at 2:21 PM, vchauras vivekchauras...@gmail.com wrote: Hello all, We had a build machine which used to install Wix3.6 msi using msiexec /qr /i WiX\wix36.msi Now, we are updating our build scripts to use Wix37.exe , but I dont know is there a way to install latest wix using command line ? Are there any options with this exe so that i can silent install wix37.exe on command line ? Thanks Vivek -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Install-Wix37-exe-using-command-line-tp7580153.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching http://RobMensching.com LLC -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn - InstallAnywhere ExePackage
UPDATE: OK, using the recommendation of creating a stub EXE I have got this working. Here's what I did in case anyone else needs to handle this type of installer. 1. Created a stub executable that manages the installation and removal of the package. The stub exe does a few things: a) Parses some command line parameters (to pass the install / uninstall). b) Launches the specified executable. c) Returns the exit code from the launched process (so burn knows if it failed or succeeded). 2. In order to determine if the actual package was installed, I used a burn file search (since I knew where the uninstall.exe file should be) and used that variable for the ExePackage/@DetectCondition. This way the package would be installed if the file wasn't found. 3. Added a Payload element for the real install package. In the end here is an example of what my WiX authoring looked like: ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:util=http://schemas.microsoft.com/wix/UtilExtension; Fragment util:FileSearch Path=[ProgramFilesFolder]MyCompany\MyProduct\uninstall\uninstall.exe Variable=ThirdPartyUninstallExecutable/ PackageGroup Id=ThirdPartyProduct ExePackage Id=ExePackageStub_ThirdPartyProduct DisplayName=Third Party Product Description=Third Party Product PerMachine=yes SourceFile=C:\Visual Studio Projects\Bootstrapper1\ExePackageStub\ExePackageStub.exe DetectCondition=ThirdPartyUninstallExecutable InstallCommand='-ExeFile ThirdPartyInstall.exe -ExeCommandLine -i silent -DUSER_INSTALL_DIR=\[ProgramFilesFolder]MyCompany\MyProduct\ -DREGISTER_UNINSTALLER_WINDOWS=FALSE' UninstallCommand='-ExeFile [ThirdPartyUninstallExecutable] -ExeCommandLine -i silent' Payload SourceFile=C:\Visual Studio Projects\Bootstrapper1\ThirdParty\ThirdPartyInstall.exe / /ExePackage /PackageGroup /Fragment /Wix So, as you can see, I used the ExePackage/@InstallCommand and ExePackage/@UninstallCommand to pass my stub EXE the information I needed to run the install or uninstall. If you are installing an InstallAnywhere package the -DREGISTER_UNINSTALLER_WINDOWS=FALSE switch prevents it from adding an entry in ARP. Another tip, for the exe stub, if you are using the http://msdn.microsoft.com/en-us/library/windows/desktop/ms682425%28v=vs.85%29.aspx CreateProcess function be sure that the first part of the command line is the full path to the executable you are launching. Hope this helps someone (and thanks for the initial suggestion)! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-InstallAnywhere-ExePackage-tp7580040p7580152.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
