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
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:
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
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: ?? ??
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
23 matches
Mail list logo