The SummaryInformation pseudo-table's row with the key valued as "11" is the
row that supplies the creation date-time of the Windows Installer file.
However, I don't see how the code could produce this error.
Could you open a bug supplying the files that are the inputs to pyro.exe
resulting in thi
Jumping to conclusions certainly is
/Thomas
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: 4. november 2009 06:49
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] How to know which InstallerVersion to use?
It is human to not "RTFM" (alo
If you want to use the WiX-supplied values, you need to have the following
element in your authoring: and have
"es-es" in your -Cultures parameter for light.exe. Otherwise, you need to
make sure your ProductLanguage is set to some LCID that identifies Spanish
so it will use the strings from the OS
At one time there were guidelines that stated that registry and program
files layouts should follow a "company name"\"product name"[\"product
version"] scheme. There was also advice to do the same thing in the Start
menu as well, although the latest guidelines in the Start menu have changed.
In th
It is human to not "RTFM" (along with all similar activities), isn't it
-Original Message-
From: Thomas Due [mailto:thomas@scanvaegt.dk]
Sent: Tuesday, November 03, 2009 4:59 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to know which Insta
Sorry if I am confusing you.
I recommend you decide upfront if your installation will be per-user or
per-machine. Don't try to make a package that is intended to be switchable.
Then author the package based on your decision.
MSI 5 (Windows 7 or Windows Server 2008 R2) is required to make workabl
Are you consuming the merge module through Merge/MergeRef?
If so, you wouldn't be able to get past this error - merge modules are
processed as part of the binding phase of the WiX build process which is well
after linking -- where you got the error.
I can suggest you two approaches:
1) Modify th
We use Wix 3.0.
In the progress dialog, there are some text showing during installation such as
"Starting services", "Copying new files" or "Stopping services". I wonder if
these text configurable based on different language?
I found these string IDs and add the translation in each wxl files.
I am trying to create an SP1 rollup MSP using these steps - Apply the same SP1
patch to both the Eval and Select SKUs of Release version separately, and then
generate the DIFFs by comparing the corresponding updated versions.
I was able to get to the point where we have the transforms (wixmst) b
It might be set in the registry (isn't everything?) but that seems to be an
implementation detail. AFAIK the correct way to get this value for an installed
product is to call MsiGetProductInfo(mailto:tim.mussch...@telenet.be]
Sent: Tuesday, November 03, 2009 11:32 AM
To: 'General discussion for
> did that complexity ... Why is the WiX manual separating content
> from structure
Markus,
I am a new WiX user, but based my gut reaction as a software engineer,
and my thin experience so far with WiX, the answer is "separation of
concerns", which is a fancy way of saying "because it's s
I have a question on how we "should" structure the directories for our
software (for loose values of "should").
Is there a guideline that prefers one of the following over the other,
given the company ACME and the program WidetApp, or is it just
tradition etc.?
1) C:\Program Files\ACME\Widg
Is this an absolute requirement? By which I mean that if you require this
behavior then you will be disabling browse choices and forcing TARGETDIR to be
what you want.
It depends what C: is intended to be. If it means you want to install it to the
same drive as Windows then you don't use the P
I was not subscribed before, and this message is in reply to
http://n2.nabble.com/Is-it-still-a-bad-idea-to-rename-your-MSI-files-td3
896724.html
I'm trudging down the path of wrapping my MSI's in EXE's that unpack the
MSI to a consistent filename, just to avoid this bug in Windows
Installer. Th
Hi -
I need to edit one of WiX's standard .IBD file (bitmap) and can't seem to find
an appropriate editor.
What's editor do i need to use in order to be able to edit .IBD file?
Thanks!
Ali
___
Just rename it and open it with paintbrush or the tool of your choice.
--- On Tue, 11/3/09, Ali Khan wrote:
> From: Ali Khan
> Subject: [WiX-users] How to edit .IBD file
> To: wix-users@lists.sourceforge.net
> Date: Tuesday, November 3, 2009, 1:47 PM
>
> Hi -
>
> I need to edit one of WiX's
On Mon, 2 Nov 2009 16:20:21 +0100, Jiang, Chunyan (GE Healthcare) wrote:
Chunyan,
> I tried to compile the sampleListbox from Wix Tutorial 10.1. I
> downloaded the source code and tried to build the dll.
For such simple jobs like this I don't like the overkill of an integrated
development envir
I have modularized my WiX project into several small subprojects using
fragments and wixlibs.
Binding together the wixlibs (and such, the s with the main
) is working well.
Now I want to modularize my translations (.wxl file).
I am binding micro .wxl files into my wixlibs using lit's -loc par
Hello,
I've found a way of introducing a product serial in the Installer. This key
is set in the registry at the default location (as arranged by MSI). Now I
want to read the key of a previous installation (at upgrade for example)
into the PIDKEY variable of my WIX script (this is not done automat
I have a merge module that was supplied to me but it has a bug in it
that means it doesn't register a com component. I am hoping to get a fix
for this but I thought I should be able to fix the problem by adding the
relevant registry keys to the host install. I have added a component and
have added
For me this more sounds like a bug in heat. IDs should be GUID -- *unique*
IDs.
Regards
Markus
> -Original Message-
> From: Nick Ball [mailto:nick.b...@grantadesign.com]
> Sent: Dienstag, 3. November 2009 16:07
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [Wi
Rob,
thank you very much for this interesting insights. Using wixlibs seems to be
the right solution unless external partners come into play.
Thanks
Markus
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: Dienstag, 3. November 2009 16:04
> To: General dis
Blair,
now I am more confused than before. On one hand you say, I shall write a
.msi that is either perUser OR perMachine, on the other hand you say that it
is very hard to do when not using MSI 5 (which is only available on Windows
7). So for me this reads like: "For a MSI beginner it is impossib
Sorry for not being clear..
I would like to have the installation in my custom folder "XYZ" rather than in
ProgramFiles folder ie., something like C:\XYZ.
I have tried using this
but the installer aborts in between :(.
Any help would be very appreciated.. Its very urgent :(
Blair,
thank you for this detailed information. It is a big help for me. Since I
don't know anything about any of the mentioned features, I doubt that I ever
will need a later version than 1.00 (100), as my software is not 64 Bit. :-)
I just have filed a request to add your list to the WiX docume
I have read both, the WiX manual and the WiX tutorial.
While the WiX tutorial is putting content (s) directly into structure
(s), the WiX manual is always separating it (s are only
used in s). As Gábor didn't know why the WiX manual authors
did that complexity, I'd like to ask this mailing list
Blair,
thank you for your comments.
If WiX makes using Merge Modules more complex than it should be, why not
improving that issue? I mean, shouldn't WiX make dealing with MSI easier
than harder?
Regards
Markus
> -Original Message-
> From: Blair [mailto:os...@live.com]
> Sent: Montag, 2.
> Markus I'd recommend setting InstallerVersion to 301 unless you want to
> either bootstrap the 4.5 installer before your MSI (or expect your
> users
> to manually install it) or you don't mind excluding users on certain
> O/S'es (this is sometimes desirable if your application has certain
> requi
I'm running into a strange issue with an interaction between an Edit control
and a default button with a custom action on a WiX Dialog. The Edit is tied to
an MSI property, and the button's custom action does some processing to
validate the value of that property. I'm finding when I make the
That compiler version should work fine. It still sounds to me like you need to
find the "precomp.obj" file, and delete it. Are you sure you deleted the .obj's
as well as the actual output directory? I'd offer other suggestions, but I
can't think of any other avenue of investigation.
-Origin
I've had a problem using wixlibs in that auto-generated (heat.exe)
libraries can end up having the same ID's for components, which then
fails to build. This doesn't happen with merge modules - which is what
I've ended up doing.
-N
-Original Message-
From: Blair [mailto:os...@live.com]
S
There are a lot of reasons not to use script based custom actions due to
environmental issues. They have a tendency to fail significantly more often
than other types of custom actions (and custom actions have a tendency to
fail significantly more than the built in support).
Personally, I recommend
Markus,
This old blog post of mine might be useful as well:
http://www.robmensching.com/blog/posts/2008/10/10/What-are-.wixlibs-and-why-would-you-use-them.
You've hit the high points already though.
On Mon, Nov 2, 2009 at 1:01 PM, Blair wrote:
> More-or-less yes, you have it right.
>
> There ar
PS: The Windows Installer .PCP files requires the File/@Id and
File/@Sequence to be stable during the patching process. That is why the WiX
toolset sorts the way it does, it ensures the MSIs will be able to be
patched. Now, IIRC, pyro is smart enough to handle the File/@Sequence
changes but the Fil
The Visual Studio team building the .NET Framework made similar
observations. They've done a serious amount of work to shrink the size of
the .NET Framework 4.0 and I'm hoping we can get some of their observations
(which seem to be identical to yours) into WiX v4.0.
Also, I am investigating what i
> Actually, yes. However, even more worrisome to me are the
> complaints
> I've *not* received from people who simply decided it was
> too big and
> didn't bother downloading it.
>
> > Doing the simplest thing that could possibly work is
> generally the
> > best approach with installers.
Ever not
Oh right. Sorry, I missed that bit. I just stubbed my toes against: "
Vista/2008 only."...
That'll teach me to read the entire thing.. (not bloody likely, but one
can always hope ;) )
/Thomas
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: 3. november 2009 08:31
To: 'Genera
In article <162de7480911021842v75b9ecc1j99622cf647134...@mail.gmail.com>,
"Wesley W. Terpstra" writes:
> On Mon, Nov 2, 2009 at 11:41 PM, Richard wrote:
> > In article <162de7480911020831o4b123747xc933d27b4fbf8...@mail.gmail.com>,
> > =A0 =A0"Wesley W. Terpstra" =A0writes:
> >> [...] For
Ah yes, you are right, looking in the log, I can see that ResolveSource
happens, but my property is never set. And so the feature is set to
Request: Null, Action: Null.
Now the full UI log sets all the search property in AppSearch. This
doesn't happen in passive mode. Why not?
BTW, I know the sco
You remember incorrectly. They ship 3.1v2 with XP SP3 (see
http://download.microsoft.com/download/6/8/7/687484ed-8174-496d-8db9-f02
b40c12982/Overview%20of%20Windows%20XP%20Service%20Pack%203.pdf) which
was also shipped in SP2 for Server 2003 (and XP64 by extension) quite
some time ago.
4.5 is shi
I am using
Microsoft Visual Studio 2005
Version 8.0.50727.762 (SP.050727-7600)
Microsoft .NET Framework
Version 2.0.50727 SP1
Installed Edition: Professional
And I have tried clean build. But it doesn't work.
Sorry, I don't know what is 64-bit or 32-bit build. How to check them?
-UrsprÃ
41 matches
Mail list logo
