Thanks for sharing Vern :-)
-Original Message-
From: Vern Graner [mailto:v...@txis.com]
Sent: Friday, February 15, 2013 5:52 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Question on multiple targets for "Upgrade ID"? SOLVED
OK, just wanted to share how I got this worki
OK, just wanted to share how I got this working.. It was a matter of
adding multiple upgrade code sections and using incrementing unique
property names like this:
Take a look at the PlanPackageBegin function in InstallationViewModel.cs (the
WiX installer BA). You'll see that it sets the request state to none if it
is the netfx package.
If you aren't using your own BA then you could just copy the appropriate
code from the NetFx*.wxs file and remove the "Repa
I have a bundle that chains a prerequisite .NET framework using the NetFx40Web
package group and an MSI and I'm using a custom managed BA. This works fine
during installation and uninstallation. The .NET framework is either already
present and detected or downloaded and installed, followed by
It might be more correct to say the issue was our legal team's reading
of the license, rather than the license itself, but we had to go on
their advice. I believe it was related to the idea that we'd be
shipping the WiX custom action DLL with our installer - but of course
you'd intended that DLL to
Steven, thanks for reply.
> Did you change the Product Id="some GUID">
Yes, the GUID is auto-generated each time when WiX compiles the
source. This is defined by the . But just for
completeness: I just generated a new GUID and repeated the test,
without success.
> DowngradeErrorMessage="A ne
Check to see if the InstallShield is a "Per-user" or "Per-machine" install and
compare that to your WiX installer. A per-user install can't be removed by a
per-machine install. If ALLUSERS isn't set or is set to 0 then that's per-user.
If ALLUSERS is set to 1 then it's per-machine.
-Origina
That's cool. I was contemplating putting in special code to work around
it but I think it will be such a rare occurrence that it wouldn't be
worth the time/effort.
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Friday, February 15, 2013 12:34 PM
To: Genera
That's correct.
-Original Message-
From: Arnette, Bill [mailto:bi...@signalscape.com]
Sent: 15 February 2013 16:55
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Solved! RE: RegistrySearch returning strange value
So it appears you leave it as a custome
Bound files are simply files that are zipped up into the wixlib.
If you have a wixlib containing a component that installs a file, you can
bind that file into the wixlib. It makes managing builds and tracking
versions of files much easier.
-Original Message-
From: Pally Sandher [mailto:pa
Personally I find a wixlib is mostly only useful if you're going to be sharing
them with a third party. They're effectively WiX's own version of merge modules
(but without a bunch of the problems merge modules have).
If your products A & B are being built from the same solution then feel free to
So it appears you leave it as a customer support issue instead of
guarding against it in your installer?
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Thursday, February 14, 2013 6:57 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re
Thanks Peter for the explanation. I created a Lib file in VS and using it
through a second installation WXS. Not sure what "bound files" are but I
will look that part up to see how I can use these.
As for the tutorial, it does not talk about lib files only fragments.
-Original Message-
There might be a wixlib example in the wix tutorial but I can't access it at
the moment.
A wixlib is like a compiled wxs file containing 1+ fragments. Instead of a
wixobj it's compiled into a wixlib. Optionally it can have the files
referenced added to the wixlib file in a cab (a bound wixlib) whi
No, that's what requesting elevation exists for.
You should be asking why you need to turn UAC off in the first place which I
suspect we can't answer.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innova
For a major upgrade you MUST change the product GUID, increase your version
number (Minor version) i.e. from 1.0.0.1 to 1.1.0.1 and use the MajorUpgrade
element.
I just use:
Did you change the Product Id="some GUID">
Comment OUT all of this:
That
Hello Again,
Figured out that libs are essentially Fragments. If there is a tutorial
somewhere that I missed I would appreciate a link. If libs are not like
fragments I would appreciate someone correct me on this misconception I have
Thanks again,
Marc
Hello,
I am in the process of learni
I want to install my first major upgrade. The older product MSI
version 1.05.02 has been build with InstallShield. Let's say the
UpgradeCode of the old product is
---5-6.
My new installer has the same UpgradeCode as the old product version.
The upgrade should be
OK. I tried MsiPackage/@EnableFeatureSelection="yes" without success.
With MsiPackage/@DisplayInternalUI="yes" it's ok but i don't it must be
used together.
Anyway MsiPackage/@EnableFeatureSelection would give a GUI ? Any way to
make it silent ?
Le %:Date:, Rob Mensching a écrit:
> Don't try to
Hello,
I am in the process of learning wix and have a question on wxLib files:
I found this link explaining why someone would use lib files:
http://robmensching.com/blog/posts/2008/10/10/what-are-.wixlibs-and-why-woul
d-you-use-them
I cannot find a good primer on how to use wxlib files
Don't try to use ADDLOCAL or the other properties. You'll get into insane
amounts of complexity trying to get that all correct during upgrades and
uninstalls. Burn will callback to your BA and request what feature states
you want if you set MsiPackage/@EnableFeatureSelection="yes".
On Fri, Feb 15
"How do I to turn off all the security systems in the bank before I rob
it?"
On Fri, Feb 15, 2013 at 5:23 AM, David Watson wrote:
> There may be a programmatic way to do this but you would need your
> installer/bootstrapper to be elevated to turn it off which would mean a UAC
> prompt before d
Your upgraded package:
[191C:2664][2013-02-15T13:12:08]i001: Burn v3.7.1224.0, Windows v6.2 (Build
9200: Service Pack 0), path: C:\ProgramData\Package
Cache\{23bfee33-60bc-452e-88f7-41dee844d1f1}\BootstrapperSetup.exe,
cmdline: '-uninstall -quiet -burn.related.upgrade
Did an install:
[191C:2664]
Sounds like you've found a bug in the Windows Installer (msiexec.exe). Not
sure there is much we can do if they are whacking our registry keys
indiscriminately.
On Fri, Feb 15, 2013 at 3:08 AM, Ogrodowski, Sabine (ehem. Frauenhoffer) <
sabine.ogrodow...@haufe-lexware.com> wrote:
> Procmon says t
"there
were some issues with the 2.0 license which prevented us from using
any WiX extensions because it effectively means distributing code from
the WiX project" - that was never the intention and still isn't.
The intention is that if you change code in the WiX toolset, that you
publish that bac
No. The signature verification code didn't change from WiX v3.6 to WiX
v3.7. This is installing the WiX toolset itself, right? I think they were
signed with the exact same certificate as well. There is no difference that
I know of.
On Thu, Feb 14, 2013 at 11:52 PM, Neil Sleightholm wrote:
> Anyo
You could pass ADDLOCAL parameter to your Bootstrapper with different
value in install and repair.
..
..
Le %:Date:, Gabriel Ivanes a écrit:
> OK. Bootstrapper allow repair command.
>
> Le %:Date:, Hans ter Horst a écrit:
> > Ah, sorry, I meant when running the MSI via the burn boo
Are you signing your bundle? If not, do so...typically AV is more forgiving
of signed files. Also, the burn engine is what writes those keys you
mention.
For reference, there are steps in the WiX CHM file that indicate how to sign
bundles.
--
View this message in context:
http://windows-instal
OK. Bootstrapper allow repair command.
Le %:Date:, Hans ter Horst a écrit:
> Ah, sorry, I meant when running the MSI via the burn bootstrapper. I have
> the MSI working like I want but I do run my MSI with user interface from
> the Bun bootstrapper, but when I run the bootstrapper a 2nd time, I o
Ah, sorry, I meant when running the MSI via the burn bootstrapper. I have
the MSI working like I want but I do run my MSI with user interface from
the Bun bootstrapper, but when I run the bootstrapper a 2nd time, I only
have the Repair and Uninstall options.
Sorry for the confusion.
On Fri, Feb
Good day,
I had this required. I used transitive components.
You could try ADDLOCAL property. Dunno know if it's available during msi
repair.
Le %:Date:, Hans ter Horst a écrit:
> Hi,
> I have a feature tree based installer that has 4 features. If I install
> during a first phase, for example,
There may be a programmatic way to do this but you would need your
installer/bootstrapper to be elevated to turn it off which would mean a UAC
prompt before disabling UAC, which I expect you are trying to avoid.
It would be a pretty poor security measure if programs could just turn it off
regardle
No and that goes completely against what UAC is all about.
Neil
>Hello,
>
>i would like to turn off the UAC before installing. Is there a way to do
>his?
>
>Greetings,
>Christoph Götz
>
>Verschlüsseln Sie Ihre E-Mails mit gpg4o für Outlook 2010
>--
In the manual at:
http://wix.sourceforge.net/manual-wix3/install_dotnet.htm
Under Step 2 it says:
"Add a PayloadGroupRef element to your bundle's chain that references the
.Net package required by your application."
The example are the just:
How shuld the PayloadGroupReference be ad
Hi,
I have a feature tree based installer that has 4 features. If I install
during a first phase, for example, features A and B, I would like to be
able to run the installer again to install C and maybe uninstall B. At the
moment when I start the installer for the 2nd time, the only option I have
i
Hello,
i would like to turn off the UAC before installing. Is there a way to do his?
Greetings,
Christoph Götz
Verschlüsseln Sie Ihre E-Mails mit gpg4o für Outlook 2010
-
Chris
Yes, it seems the bundles are detecting each other. There are 2 log files
when trying to do an upgrade (actually 3 if you count the log file for the
*.msi file also).
The first log file (111BootstrapperSetup_20130215131202):
[0044:18DC][2013-02-15T13:12:02]i001: Burn v3.7.1224.0, Windows v6.2 (Bu
Hi, Is it possible within WIX to create a new Isapi Extension when
installing a web application. At the moment I am using the command line but
I have looked at WebApplicationExtension and wondering if this is what I
need?
Kind Regards,
Natalie Carr
--
That works great!
On Fri, Feb 15, 2013 at 11:41 AM, Peter Shirtcliffe wrote:
> Create a directory with the ID set to the same as the MSIProperty name,
> i.e.
> INSTALLLOCATION. When the bootstrapper passes the property to the MSI, it
> overrides the directory's default path in the MSI
>
>
>
Procmon says the registry keys get deleted by the msiexec process. I haven't
worked with procmon before, so what information could help you?
The problem is not reproducible on all XP machines. If window update KB982524
is installed we don't see this behavior. If a machine hasn't installed this
>From my experience, the current license on WiX 3.6+ is fine (there
were some issues with the 2.0 license which prevented us from using
any WiX extensions because it effectively means distributing code from
the WiX project), but your legal situation may be different.
Does your company have a copyr
Create a directory with the ID set to the same as the MSIProperty name, i.e.
INSTALLLOCATION. When the bootstrapper passes the property to the MSI, it
overrides the directory's default path in the MSI
-Original Message-
From: Sam Boman [mailto:s...@samb.se
I want to pass the Options Location in the Bootstrapper UI (
WixStandardBootstrapperApplication.RtfLicense) to the MSI:
In Bundle:
How to pickup this property in the MSI (I go for a MSI without a UI, and
let the bootstrapper be the only visible UI to the user)?
Hi,
I have a very basic doubt regarding the license structure of this project.
I am planning to use Wix Toolset for creating Installer (*.msi) for one of
our commercial application.
Does this has anything to do with Ms-Rl license? I am sorry if this
question does not make any sense.
Thanks
Prave
I write a merge module that includes a local server MyProg.exe. This
server has a lot of COM Classes that must be registered.
I know the method with RegSpy to generate a registry file and to
harvest with "heat reg". This has the drawback that it generates each
registry value as an indivual compone
45 matches
Mail list logo
