What causes the paths
in HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components
to contain question marks instead of colons?
For example, I find paths that look like
this:
C?\Program Files\Common Files\Microsoft
Shared\VBA\VBA6\VBACV10.DLL
instead of
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 provides. So, if
you don
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
[mailto:[
Probably due to your delayed mail –
we’ve already got a bug opened against him J
From: Rob Mensching
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 13, 2006 7:08
PM
To: 'Christopher Painter';
[EMAIL PROTECTED]; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Dark Bug?
If I remember the ref counting properly, and looking at the MSI docs for the
msidbComponentAttributesSharedDllRefCount bit:
MSI ref counting just works, on components, and I don't know if the OP was
thinking of MSI ref counts or the SharedDlls ref counting (which can cause
files to remain after an
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
Can you open a bug on
the web link being broken and assign it to "fregro". He takes care
of the online manual creation.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Christopher Painter
Sent: Tuesday, June 13, 2006 5:48
PM
To: [EMAIL PROTECTED];
wix-users@lists
I agree about VSI MSM's... unfortunatly I'm stuck with about 700 of them. I'm also have about 80 MSM's that were statically written using ORCA because it couldn't be done in VSI and the developer didn't want to use InstallShield. It was killing me to be storing MSM's in ClearCase so I tried ado
Hi,
First just a warning - this is my first foray into wix.
I am trying to build a wxs file to install an asp.net web service and an
asp.net web app that is a front end to it.
If I understand the logical and constructs
correctly then each of these is a and because I want the
user to be able t
There’s an open bug against simple
xsd types not working – for now you should just use wix.chm instead –
it should have no broken links.
Derek
From: Christopher
Painter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 13, 2006 5:48
PM
To: [EMAIL PROTECTED];
wix-users@lists.sou
You have to forgive me, many terms are overloaded or expressed differently when you go from InstallShield to MSI to WiX. ( For example SystemSearch, AppSearch, RegLocator, RegistrySearch) I tried to make sure that I understood the way WiX expresess things before posting but unfortunatly I stu
Upon further investigation into this
issue, you appear to be correct about the correlation of the Revision Number
summary info property and the modularization guid. This means that the
way WiX currently generates merge modules is wrong (and has been wrong for a
very wrong time).
I need
FYI, my mail is coming
very slowly and out of order... so if I seem to be answering mails that were
already answered, feel free to ignore me.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching
Sent: Tuesday, June 13, 2006 3:59
PM
To: 'Christopher Pain
The PID_REVNUMBER thing
sounds like a bug in dark.
If you have a valid
MSI/MSM file I do expect dark.exe to be able to decompile it. However, candle
appears to be far more exact about what it allows one to put into an MSI/MSM
than some of the other authoring tools out there (I know thi
So here's how things look from what I've seen recently:
WiX 2.0
- the core tools are basically done - we haven't done anything but bug fixes
in there for ~6 months now
- the custom actions are still being actively worked on albeit at a slower
pace than years ago - the focus recently has been on bu
The package code of an MSM file is not the same thing as
the Module/@Guid.
PackageCode
The decompiler never persists a PackageCode because its
supposed to be unique for every single MSM/MSI/PCP file. Even if
you link the same MSI twice in a row, the guid is supposed to change. That
is wh
Frederik:
We are using version 2.0.3309.0. We began using it due to limitations that
we encountered with the standard Web Installer projects in Visual Studio
2003 (namely issues with IIS deployments).
We have used it to create the deployment packages for four web site / web
service applicatio
In a previous message I talked about Dark not extracting the Package ID from MSM's. Try this: ( Using Dark 3.0.1703.0 ) and Orca 3.0.3709.371 Create a New MSI database using ORCA and look at the Summary Information Stream to validate that it was a ProductCode. Save the database as an MSM.
[This message is BCC'd to wix-devs for those who are not subscribed to
wix-users, but I think it is worth keeping the discussion on wix-users
only]
Hi,
Text quoted from Derek Cicerone ("Re: [WiX-users] Localized version of
License.rtf"):
> The other option is to move to WiX 3.0. Work on the core
Not to get into a religious debate over dogfooding, but personally I don't install less then production ready installs on my dev box. That's what I have integration/test machines and/or imaging/VM snapshot tools for. Derek Cicerone <[EMAIL PROTECTED]> wrote: Its probably good to note that msi
I made this comment because Rob said:"Have you looked at dark (the WiX toolset decompiler)? Dark v3 is particularly solid. It will drop all of the files and .wxs authoring in such a way that the compiler and linker can put it all back together."This implied an IJW symbiosis between Dark and Candl
Is it possible to create an uncompressed install image by
running an admin install? (I'm honestly not sure how well it would work -
just an idea)
Derek
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Simon
TopleySent: Tuesday, June 13, 2006 8:29 AMTo: 'Christopher
Painte
Its probably good to note that msizap should be used sparingly because it's
a bit dangerous - it sometimes goes overboard in what it removes - so you
really want to make sure this tool is only used on development machines.
Derek
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL P
Christopher,
I'm sorry, but I think its a particularly unfair
comment to say that a bug in dark was "scoffed to the side". I believe the
particular issue you are referring to dealt with dark creating output that when
compiled immediately produced errors. I would like to explain why that
Kalappa Pattar wrote:
I want to read the
command line arguments that are passed to
msi file .
Based on the
command line parameter I want to set a property in my wix
file.
MSI supports this natively. You can set public properties at the
MSIEXEC command line:
Peter G. Sakhno wrote:
> Does MSI increments the file's reference count if I install DLL, EXE and
> any other files into [*:\Program files\My Product\System] directory not?
>
MSI maintains a reference count on every component it installs (except
permanent components). That's separate from the
Hi All,
This
might be simple thing, but I do not know how to do this.
I want to read the command line arguments that are passed to
msi file . Based on the
command line parameter I want to set a property in my wix
file.
Can someone suggest me how to do this?
Best Regard
Tweaking feature states via a custom action is a little heavy and pretty
dangerous in terms of getting all the behavior exactly right. If you have
two components that can never be installed at the same time, you could also
consider giving them conditions such that they never get installed
simultan
That's a good one-off solution, but it would be cool if we could create a
solution in the extension itself so that everyone can leverage it without
additional work.
Putting the license text in the wxl file won't be good enough in WiX 2.0
because there is no ability to override that text. So you'd
In terms of the files they both yield there is no
difference, but as you say the "XML" that comes with it is the real difference.
I have not tried to rebuild the output from Dark yet as I'm still wondering if I
want to use it at all. The reason I want to do this extract is so that I can
buil
MSI2XML and Dark are different in that MSI2XML only attempts to transform MSI schema and data into XML format while Dark attempts to translate MSI schema/data into an entirely different schema that just happens to be in XML format. InstallShield uses MSI2XML ( there is even a credit in the help
MSI2XML and Dark are different in that MSI2XML only attempts to transform MSI schema and data into XML format while Dark attempts to translate MSI schema/data into an entirely different schema that just happens to be in XML format. InstallShield uses MSI2XML ( there is even a credit in the help
Sure, I've tried that. Unfortunatly Dark and Candle disagreed on what `valid` MSI code was and the compiler and linker couldn't reassemble what Dark created without alot of hand jamming. I even reported this as a bug but had it scoffed to the side as `works as designed.`Rob Mensching <[EMAIL PROT
Title: Message
Hi,
Yes,
I was talking about Help 2.0 Hxs files.
I implemented the functionality by modifying
MSHelp2_RegTables__RTL_---_---.msm file appropriately
and also I used HTML_Help_Registration__RTL_---_---.msm.(which are distributable)
And now I am able to regist
Bah, just re-read your original message. Yes, you'll need a custom
action to control this. If you are using the feature tree, you will
want MSI 3.0+ I believe so that you'll have access to the extra events
for the feature tree in those versions.
On 6/13/06, Joannic Laborde <[EMAIL PROTECTED]> wrot
Hi ...
I had several problem (one year ago) and here is my sulution:
In main wxs file I have LicenseDialog and one control is :
Then I have script (in ruby) which will copy verbatim the RTF text
of the License (in correct language) into corresponding wxl file.
The wxl file itself is not very "
It is not possible; you'll have to use a custom action to unselect a
feature when the other is selected (using MsiSelectionTreeSelectedAction
and MsiSelectionTreeSelectedFeature). Unfortunately, the SelectionTree
doesn't refresh itself when a feature state is modified in a custom
action, so you wil
Thank you, but I think I have not expressed myself good enough.
I have already one what you describe.
I also want the user not to be able to select option 1 at the same time as
option 2
Met vriendelijke groeten,
Yves Hanoulle, Project-Coach
http://www.paircoaching.be/blogs
www.hanoulle.be 0476
Put the features in seperate components. Have them on the same install
level and use the feature tree to control which features are
installed.
AFAIK there is nothing the MSI supports that WiX doesn't.
On 6/13/06, Yves @ Hanoulle <[EMAIL PROTECTED]> wrote:
> In my install file I have 2 features th
In my install file I have 2 features that are mutual exclusive. (I do not want
to have them both installed at the same time.)
(Yes it needs to be 1 install file.)
Is there a way to do this, (preferable using wixui_mondo)?
Yves Hanoulle
___
WiX-use
This guy really does role 20's, I'll give it a
spin
From: Rob Mensching
[mailto:[EMAIL PROTECTED] Sent: 13 June 2006
10:20To: 'Simon Topley'; 'Christopher Painter'Cc:
wix-users@lists.sourceforge.netSubject: RE: [WiX-users] Extract files
from msi (Msiexec, not WIX issue... .)
Have you lo
Have you looked at
dark (the WiX toolset decompiler)? Dark v3 is particularly solid.
It will drop all of the files and .wxs authoring in such a way that the compiler
and linker can put it all back together.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Simon T
I have had limited success with MSI2XML. The latest
build seems to have installer realted issues but the build before that is
stable. It does extract all teh files (including files desine for the windows
and system directory, sadly it names them all by the File ID, I suppose I could
go throu
Hi all,
I have a question regarding the way to reference a
merge module. Based on a wix tutorial i saw on the
web, http://www.tramontana.co.hu/wix/lesson4.php#4.4 ,
the author wrote a separate merge module file which
includes this line :
In the main source file, the author actually
references t
>> Could we please start this discussion on wix-users instead of inside this
bug? It would probably be
>> more efficient to just talk about this there.
Agreed.
Ok, can someone tell me how to find a solid solution for Wix2.0 as for the
the problem described below?
Or is it safe enough to switch
45 matches
Mail list logo
