'Scheduling.exe' though, so beware of ID
clashes.
-Original Message-
From: Sean Hall [mailto:rhal...@hotmail.com]
Sent: 16 July 2013 01:41
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Newbie question
Use a .wxi file. For more info, lo
Use a .wxi file. For more info, look at this StackOverflow question
http://stackoverflow.com/questions/8495903/how-to-define-a-global-variable-in-wix
Sean
> Date: Mon, 15 Jul 2013 16:46:13 -0700
> From: kpet...@otaksoft.com
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Newbie q
ler XML toolset.
Subject: Re: [WiX-users] newbie: how to reference variables ? (the doc is
confusing)
Yes i have a with a referencing 4 ExePackage using
PackageGroupRef
2013/5/29 Wesley Manning
> What is a fragment: you mean wix fragment? You say you have 4 exe to
> install so you are usi
alled before running your BA.
-Original Message-
From: Benjamin Mayrargue [mailto:benja...@vapolia.fr]
Sent: Wednesday, May 29, 2013 11:38 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] newbie: how to reference variables ? (the doc is
confusing)
Yes i h
e [mailto:benja...@vapolia.fr]
> Sent: May-29-13 8:08 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] newbie: how to reference variables ? (the doc is
> confusing)
>
> i think i misundestand something in wix philosophy.
>
> I have 4 ex
: Re: [WiX-users] newbie: how to reference variables ? (the doc is
confusing)
i think i misundestand something in wix philosophy.
I have 4 exe to install. I've created a bundle and 4 fragments.
All is working nicely.
Now i want to conditonally add a registry key when one of the fragme
i think i misundestand something in wix philosophy.
I have 4 exe to install. I've created a bundle and 4 fragments.
All is working nicely.
Now i want to conditonally add a registry key when one of the fragment is
"executed".
So i added this to the fragment:
Well, the bundle will *take any MSIs or other packages specified in your
Chain element** *and bootstrap them. It doesn't exactly create an MSI
itself.
It might be best if you give more details about what you're trying to
achieve, and where you're trying to use the above Condition element?
On 29
100% understood !
This means a 'bundle' creates a msi bootstrapped in an exe.
B.
2013/5/29 John Ludlow
> I think where you're getting confused is that there are more than one type
> of "variable" in WiX. Firstly, there are preprocessor variables and
> condition, which are referenced like thi
I think where you're getting confused is that there are more than one type
of "variable" in WiX. Firstly, there are preprocessor variables and
condition, which are referenced like this:
$(var.VariableName)
!(var.LateBoundVariableName)
$(env.EnvironmentVariableName)
!(loc.StringID)
These a
That isn't WiX toolset code. Looks like IExpress stuff. I thought IExpress
was dead because it contained security vulnerabilities in it. I haven't
heard of anyone using IExpress for a few years now...
On Tue, Feb 26, 2013 at 1:09 PM, james pruett wrote:
> Can anyone point me to how I debug this
Adding your Forms project as reference to the Wix setup project just
makes the output from the Forms project (exe) available to the Wix
project (var.ProjectName). You still need to tell Wix things like: what
files to include in the MSI that it generates, what kind of UI to use
for dialogs, etc.
Fo
The concept of harvesting across project references is still a bit nascent
in WiX. We tried a couple experiments in WiX v3.5 but started slipping into
a rabbit hole of issues. Things that you would expect to just work don't.
So, the harvesting feature was turned off in WiX v3.5 and you have to
expl
Personally I'm not a fan of defining an installer by scanning at build time.
It's not deterministic enough for me. I'm also not really a fan of using
project references. If you are interested, take a look at IsWiX over at
http://iswix.codeplex.com. Take a look at the source code and see how
s for and loads the .Net you
require.
Good Lucl
-Original Message-
From: Bruce Cran [mailto:br...@cran.org.uk]
Sent: Tuesday, November 23, 2010 1:47 AM
To: General discussion for Windows Installer XML toolset.
Cc: t-gr...@microsoft.com
Subject: Re: [WiX-users] Newbie to Wix for MSI inst
otland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: Bruce Cran [mailto:br...@cran.org.uk]
Sent: 23 November 2010 09:47
To: General discussion for Windows Installer XML toolset.
Cc: t-gr...@microsoft.com
On Tue, 23 Nov 2010 08:10:33 +
Grzegorz Borczuch wrote:
> The new visual editor for WiX was released lately and was announced
> here on this mailing-list: http://sharpsetup.eu/
I'd be interested to know how many computers running XP will
have .NET 2.0 installed already - unfortunately I get
Hi Kenneth,
The new visual editor for WiX was released lately and was announced here on
this mailing-list:
http://sharpsetup.eu/
Generally it consists of two plugins, one for VS 2008 and the other one for VS
2010.
>From what I saw, it allows you to create quite advanced installers. I didn't
>n
amazingly, this list still seems mostly accurate:
http://robmensching.com/blog/posts/2007/11/20/WiX-editors
On Mon, Nov 22, 2010 at 10:06 AM, Kenneth Tse wrote:
> Hi,
>
> I am new to Wix and this community and would like to ask if there is any
> GUI IDE that help to develop the Wix installer (i.
We schedule RemoveExistingProducts after InstallValidate, so it should be
safe to change all component ids.
Are there any issues upgrading 63-bit to 64-bit (as far as Windows Installer
is concerned)?
On Mon, Sep 6, 2010 at 23:34, Rob Mensching wrote:
> If you schedule your RemoveExistingProduct
If you schedule your RemoveExistingProducts early, that removes the previous
version of the product before installing the new one. Essentially that gives
you a clean slate to rev all of your Component GUIDs.
Pretty much all the other options mean you have to be very careful about
managing your Com
I have a few more questions. We have a 32-bit installer today with all
component ids explicitly specified. We are planning to move to 32/64 bit
installer (mutualy exclusive) with the ability to upgrade current
installations (major upgrade).
1. Should we update explicit component ids to "*"?
2. Wha
SHA1 hash of the target path. It took us a long time to come up with it but
we finally got it. You can see the code in wix\src\wix\Binder.cs -
Binder::SetComponentGuids()
On Sun, Sep 5, 2010 at 8:59 AM, Alex Ivanoff wrote:
> > No. "*" component guids are stable, not randomly generated.
>
> If the
> No. "*" component guids are stable, not randomly generated.
If they are stable how are they generated and where the actual values
are stored? Can you explain this?
--
This SF.net Dev2Dev email is sponsored by:
Show off
On 03-Sep-10 01:59, Andres Juarez wrote:
> Ok, so if I use "*" as component GUIDs, this means that small updates are out
> of the questions for this approach, right?
No. "*" component guids are stable, not randomly generated.
> If a 32-bit component is contained in both a 32-bit installation
nt IDs, just as 32- and 64-bit
products should have different product codes.
Or am I reading this wrong?
Thanks
Andres
> Date: Thu, 2 Sep 2010 08:40:48 -0400
> From: b...@joyofsetup.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Newbie x64 msi question
&g
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Newbie x64 msi question
>
> Hi,
> I have recently made a 64 bit MSI from a single source and I started out
> by following
> http://blogs.msdn.com/b/astebner/archive/2007/08/09/4317654.aspx
>
> The trick to ma
On 30-Aug-10 01:36, Andres Juarez wrote:
> So, running candle with teh -arch switch does take care of marking the
> components at 64 bits, but if using the same Wix source file for the
> 32 and 64 bits installer with the only difference of the candle -arh
> switch, the Components GUIDS for the
Do component GUIDs have to be different?
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: Tuesday, August 31, 2010 03:54
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Newbie x64 msi question
Hi,
I have recently made a 64 bit MSI from a single source
rez [mailto:andresj_...@hotmail.com]
Sent: 30 August 2010 06:37
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Newbie x64 msi question
Hi Bob,
In your post
> http://www.joyofsetup.com/2010/05/14/working-hard-or-hardly-working/.
> Use the -arch switch and you get smart defaults.
DS per components, I am
almost sure we do, but just asking.
Thanks
Andres
> Date: Sat, 7 Aug 2010 10:56:31 -0400
> From: b...@joyofsetup.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Newbie x64 msi question
>
> On 8/4/2010 9:57 AM, Pally Sandher wrote:
>
On 8/4/2010 9:57 AM, Pally Sandher wrote:
> You need to set the Win64 attribute on your components. If it's not set
> they default to 32-bit components in an x64 package.
> An easy way to do it is to use a pre-processor variable set to "no" or
> "yes" whether you're building x86 or x64 packages res
Check out the "heat" tool.
-Original Message-
From: Satyaprakash J [mailto:sat...@smartek21.com]
Sent: Friday, August 06, 2010 1:00 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Newbie question
Hi,
Please let me know if automati
Hi,
Please let me know if automatic updating of wxs file is available.
Thanks
Satyaprakash J
-Original Message-
From: Satyaprakash J [mailto:sat...@smartek21.com]
Sent: Thursday, August 05, 2010 8:05 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users
You need to set the Win64 attribute on your components. If it's not set
they default to 32-bit components in an x64 package.
An easy way to do it is to use a pre-processor variable set to "no" or
"yes" whether you're building x86 or x64 packages respectively. Then you
can simply use something like
On 2/28/2010 10:42 AM, Information Vision wrote:
> How can I get the setup to create app shortcut name and app target folder
> name based on the version of the app? Basically I need each version of the
> app to go into its own target folder and have its own unique shortcut name.
>
Use a prepro
Curt Holden wrote:
> Property="_BrowseProperty" Value="[UI_CONFIG_INPUT_DIR]"
> Order="1">1
>
...
> Width="320" Height="18" Property="UI_CONFIG_INPUT_DIR" Indirect="yes" />
>
And indirect property means that the property value is the name of
another property. Y
If you use the SqlScript element it never installs the files on disk.
Unfortunately, it does have a bit of a performance issue so the really
big files might run really slowly.
Otherwise, I think you're looking at creating a very complex CustomAction.
Tom Crozier wrote:
> I have several large (1
kkmca wrote:
>> My question is do i need to create a component reference to these files
>> created after installation in order to remove them?
>>
No, you just need a component; it doesn't have to be a component that
installed the files.
--
sig://boB
http://joyofsetup.com/
--
versioned files prior to installing the "new"
files.
Chad
-Original Message-
From: kkmca [mailto:[EMAIL PROTECTED]
Sent: Friday, September 26, 2008 1:11 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] newbie question about removing files created by
application
kkmca wrote:
>
> I have some birt functionality that creates a number of files and
> directories under web inf that remain after uninstall.
>
> I understand that i need to explicitly remove the files. I understand that
> the removefiles node requires a component parent and since these files
>
Alpert, Stephen R (GE Healthcare) wrote:
> The system cannot find the file "MyApplication.exe" which is the
> reference above (var.MyApplication.TargetFileName)
>
TargetFileName contains just the file name; you need to use TargetPath
like your File element.
--
sig://boB
http://joyofset
kkmca wrote:
> i added the configuration to the wxs for the custom action and the installer
> fails to complete - the logging is crytpic
>
Make sure you're getting verbose logs. Then search for "return value 3"
to find the point of failure.
--
sig://boB
http://joyofsetup.com/
---
Weinstein, Scott wrote:
> I've attmpted to add
> After="FindRelatedProducts">NEWAPPFOUND
> But I have no UI for this package.
>
> Could that be the problem?
>
No, with OnlyDetect="yes" there won't be any attempt to uninstall the
newer version. But it might be interesting: Try installi
e?
--Scott
I've updated my .wxs to the following -
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Tuesday, June 03, 2008 1:05 AM
To: General discussion for Windows Installer X
I recommend going through the WiX v2.0 tutorial (
http://www.tramontana.co.hu/wix/) and making a localized project, then
convert to WiX 3 format.
That being said, here's the WiX 3 locale files (4 of them have been moved to
the new format, the rest you have to modify but those are easy changes).
ht
> I'm totally newbie about WIX. I've just downloaded the last v3 version
> (3.0.2925.0) and I'm playing around with it.
That's a pretty old release, you get the latest drop here:
http://wix.sourceforge.net/releases/
> Moreover, if i try to define
> any other Culture in the Light setttings (
Weinstein, Scott wrote:
> Here's what the log has:
>
> MSI (c) (D0:84) [09:55:37:131]: Doing action: FindRelatedProducts
> MSI (c) (D0:84) [09:55:37:131]: Note: 1: 2205 2: 3: ActionText
> Action 9:55:37: FindRelatedProducts. Searching for related applications
> Action start 9:55:37: FindRelatedPr
ussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] newbie question about uninstalling
Weinstein, Scott wrote:
> For some reason my install packages is not detecting the prior
install,
> and the upgrade process is not working. I'm unable to see what I've
done
> w
Weinstein, Scott wrote:
> For some reason my install packages is not detecting the prior install,
> and the upgrade process is not working. I'm unable to see what I've done
> wrong and hoping it's a simple thing.
>
Generate a verbose log during installation of the upgrade package and
see what
One small difference that I can see between yours and mine which is working
is that you don't specify the Language in your UpgradeVersion elements.
Also, this isn't required to upgrade, but to prevent downgrade:
NEWAPPFOUND
Just making sure you had that too.
On Fri, May 30, 2008 at 9:36 AM,
Tris Hodges wrote:
Error 1 Unresolved reference to symbol 'Property:URadioButtonGroup2'
in section
'Fragment:'. E:\Developments\WixTest\WixProject\WixProject.wxs 78 1 WixProject
RadioButtonGroup's Property attribute points to a Property element
defined elsewhere; the error is that it can't fi
mark.modrall wrote:
I was just wondering what did if not flag missing
dependencies.
It writes rows into the ModuleDependency table, but WiX doesn't read
them at the moment.
--
sig://boB
http://joyofsetup.com/
-
This SF
I was just wondering what did if not flag missing
dependencies.
Thanks
Mark
From: Mike Dimmick [mailto:[EMAIL PROTECTED]
Sent: Monday, January 28, 2008 5:36 PM
To: mark.modrall; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] newbie question
If you&
If you're merging modules written in WiX, and those modules are not shipped
separately to third parties, consider rewriting them as Fragments. You can
precompile a fragment into a .wixout file and simply link those together.
You can assemble one or more .wixout files into a larger chunk of
function
On 10 Oct 2007, at 11:55, Anton Filippov wrote:
> Hi.
>
> msiexec /i ...msi /quiet TARGETDIR=C:#Temp
> ?
Is that # meant to be a backslash?
Cheers,
Chris
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping thr
Hi.
msiexec /i ...msi /quiet TARGETDIR=C:#Temp
?
On 10/10/07, Rad Ricka <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> sorry for asking a newbie question; but googling didn't help much.
>
> Could somebody please point me to an example that allows specific path for
> TARGETDIR dir when running msiexec
DirectorySearch and FileSearch?
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jessi Darling
Sent: Friday, September 21, 2007 13:39
To: wix-users
Subject: [WiX-users] Newbie Question
Is there a way that I can search for a file that exists on the server without
having to hard code
Mike,
Given what you describe, I assume you are using a property for the
shortcut name (and that property can be modified by the user interface).
Unfortunately, Microsoft installer does not retain any knowledge of
properties from one execution to the next, and that is why the value for
that prope
Title: RE: [WiX-users] NEWBIE
problem
That's why you have
Features. They tie groups of Components together.
That said I'm not one
to defend the data model of Products -> Features -> Components. I
have issues with it, but it's what the Windows Installer
Title: RE: [WiX-users] NEWBIEproblem
Yes it's just odd to think
about half of a partial class being in one component and the other half in
another when neither can work without the other :-)
thanks very much for the quick reply.
outstanding service! :-)
From: Rob Mensching
[m
More generally Components are "small" and Features are "things users can
turn on and off". So, typically a Feature contains many Components.
Also, Components install everything to a single directory. So if you need
to install to different Directories you need different Components.
Does that hel
62 matches
Mail list logo
