Hi there,
I have a problem, I need to specify the same Registry value, but the
value has to be different in the separate Features, this - however,
generates a error when trying to compile the project.
I Have Feature A and B.
Feature A is always installed, as a core component, and feature B gets
I want to know if I can search for a file in system path.I am trying to detect if Oracle is installed on a system. With all the
different Oracle installation types out there, only surefire way seems
to try load OCI.dll and hope that Oracle is installed correctly
if it loads without error.One
Title: What is your experience with version 3.0.2128.0?
Hi all,
With version 3.0.2128.0 WiX saw some new features, most importantly the improved version of Votive and Derek's last work.
It seems most people are quite succesful with this version of WiX and I've seen quite some reports of
Hi,
Does anyone know how I can set a dialog textbox value to the local computer
name.
I try to set its value to [ComputerName] but that doesnt seem to work.
It always sets the value to that of the property behind.
I can't see a way to initialize the property behind the text box to the
local
On 09.10.2006 11:39, Frederik Carlier wrote:
Hi all,
With version 3.0.2128.0 WiX saw some new features, most importantly the
improved version of Votive and Derek's last work.
It seems most people are quite succesful with this version of WiX and
I've seen quite some reports of closed bugs
I am switched to WiX v3 and now I can not find any localization files.
Where do I have to look or there are important changes? If anything was
changed how do I have to do localization now?
-
Take Surveys. Earn Cash.
The localizations have been moved into the .wixlib embedded in
WixUIExtension.dll. If you want to use the standard localizations,
specify -cultures:xx-xx on the light.exe command line, instead of -loc,
where xx-xx is the language you want to use, for example en-US.
--
Mike Dimmick
It sounded very difficult to try to
upgrade wxs files from v2 to v3. In my WXS files, I have registry element,
database, xml file, virtual directory, file, directory, service.
Please advice.
Hesheng Bao
From: Mike Dimmick
[mailto:[EMAIL PROTECTED]
Sent: Monday, October
I set up a Virtual PC to build Wix 2.0.4415.0. It builds and runs with
no problems.
However, when I copy the executables to my development machine, I get
the following error:
C:\Program Files\Wixcandle
Unhandled Exception: System.IO.FileLoadException: Could not load file or assembl
y 'candle,
Hello,
It seems I have found a bug in Tallow.exe. When it comes to generating multi
string attributes I get something like this:
Registry Root=HKCR
Key=ldapcom.LDAPTypeValue\CaseInsensitiveAttributeType
Value=System.String[] Type=unknown/
Original ATL registry script is:
ldapcom.LDAPTypeValue
[I posted this on microsoft.public.platformsdk.msi last week, but didn't get
any bites. Maybe wix-users will have some advice.]
I'd like to get some advice from the MSI gurus. I'm using WiX, but my
question is really about the best way to [ab]use the MSI engine.
I'm trying to migrate an
If the property doesnt exist in the first place, the checkbox is set to
unchecked.
If you check the checkbox, the property is actually created by MSI.
I think the checkbox value is linked to the existence or non existence of
the property.
fregate wrote:
Thanks for aswer. It works.
And
Hi,
I've read through some of the localization threads but I have
the impression that localization is (only?) understood as a static
process, that means that I can create different MSIs each having a
different language GUI.
I would like to have ONE MSI with different languages where the
So if we make the MSI install for all
users.. we should be able to create a new run key entry without hitting the
redirection problems?
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Friday, October 06, 2006
7:49 PM
To: Jeff MacDuff
Cc:
Thanks, it works OK now. I needed to do some minor changes to the
source for test purposes.
On 09/10/06, Mike Dimmick [EMAIL PROTECTED] wrote:
The private key is not distributed with WiX sources and so the
executables are delay-signed. This attaches the public key token and
reserves space for
Christer Solskogen wrote:
It seems like wix dont like to be run from PowerShell/Monad.
I had to run it with:
D:\bin\wix\light.exe -ext WixUIExtension "-cultures:en-us"
HelloWorld.wixobj
Can you post
a bug? I'm not sure if we can do anything to make PowerShell happy
but if we can, we
Alex Mendes da Costa wrote:
My package is not language-neutral. ProductLanguage is set in my MSI
to 1033.However, the dialog box lacks strings unless I explicitly
add the appropriate entries to the error table.
What do you have Package/@Languages set to?
--
sig://boB
http://bobs.org
Peter G. Sakhno wrote:
How to find if a product is already installed if it's Product Id is
known? Should be implemented some DLL/EXE-based CA or there are any
standard MSI commands available?
The same about merge module. I want to find out if any copy of
particular MSM (defined by its
Alexander Gnauck wrote:
which means I need a very simple solution to create transformations
without Orca.
Derek wrote the beginnings of transformation support in the Torch tool.
It's designed to create a transform between two MSI packages or from a
.wixout you can create with Dark. At the
Suraj Barkale wrote:
I want to know if I can search for a file in system path.
You can use FileSearch to find a particular file with a version range
but it doesn't support searching just the path. The alternative is to
search a tree, such as ProgramFilesFolder, but that won't find
directories
William Jones wrote:
I came up with a solution, but I'm not sure it's the right one. I
generate a new product code on every build (so every build looks like
a major upgrade). I detect when I'm doing a week-to-week upgrade and
sequence the RemoveExistingProducts action for that case, as
Jeff MacDuff wrote:
So if we
make the MSI install for all
users.. we should be able to create a new run key entry without hitting
the
redirection problems?
AFAIK, redirection is used only when a non-elevated user tries to write
to system locations. That said, I'm not a
I'd take a guess that PowerShell is somehow messing up the
parsing of the : and giving the two arguments "-cultures" "en-us", and that
light's command-line parser then interprets "en-us" as being a source file for
it to process. It then fails because it can't find the file.
This parameter
Thanks for the advice Bob.
Turned out to be one of those ID10T errors. I was installing a Windows
Service whose function is to monitor a Microsoft Message Queue. It helps to
name the MQ correctly lest your service will fail to start.
David Adams
MSN MessengerID: [EMAIL PROTECTED]
From:
Hey, worked a treat, thanks.
Bob Arnson-3 wrote:
gcoates wrote:
I can't see a way to initialize the property behind the text box to the
local computer name either as CustomActions seem to run after the UI has
been displayed.
You can schedule a custom action to run early in the UI
The closest that I get is setting existing features in the tree to
unselected (Do not install) based upon User interaction in previous
dialogs. The feature list is static, but the items selected by default on
the Customize dialog are controlled by the prior interaction.
I'm not sure that
Thanks allot!
I'm not warring about size of the package. I have another case.
The runtime part of our software can be shipped as a stand alone MSI or
as a merge module. And the point is that this two edditions (MSI MSM)
are incompatible. Standalone runtime can not be installed on the
computer
Bob's suggestion is one way. You could, for example have a dialog box with a checkbox for each feature, and show/hide them as you like based on a .
Another option is to use a custom action -that's what this _vbscript_ code does:
Set installer = Session.Installer
Set database = Session.Database
I might be missing the point but don't you just include this:
UIRef Id=WixUI_ErrorProgressText /
You will also need to build it with 'wixui.wixlib -loc WixUI_en-us.wxl'
on the light command line.
Neil
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
What is the equivalent tool of tallow in Wix v3 and how do I extract
registry entry from COM components? Maybe there is a new way of
installing COM components I should know? So many questions and so less
answers. Where can I find a documentation about WiX v3? The tutorial I
have describes only
WIX Version: 2.0.4415.0
My installer will install two different products (companion
products). While the user would normally install one on one machine and
the other on another machine, they could install both on the same
machine. I need to modify the MACHINE.CONFIG regardless of which
It is a PowerShell issue. I have do to the same
quoting when using NAnt when I want to pass a property on the command
line. Ex. Nant -D:property=value in cmd.exe has be typed in
PowerShell as Nant "-D:property=value". Thinking about it, it may have to
do with how it parses the command line
There's a vbscript WiGenXfm.vbs in the Windows Installer SDK.
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alexander
Gnauck
Sent: Monday, October 09, 2006 1:45 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] create
My first thought would be to create a third feature, which the
user has to install, which then does the modification of machine.config.
Then, you could put your xml modification in a new component, which gets
installed with the must install feature.
From:
[EMAIL PROTECTED]
Bob Arnson wrote:
Sigurd Stenersen wrote:
Is it at all possible to modify the number of features in the
feature tree, from a DLL or using some sort of action ?
I'm able to set the state of features, but I would like to present
users with different trees depending on selections made in a
We started out today by logging the file accesses and came up with
some odd results that we're not sure what to make of... If you interpret
the good log file, you see that three different msiexec processes
access the file one after the other. However, the bad log file shows
that one of the
I ported your code to C++ and it does indeed work.That is, it hides features.It doesn't seem to work for features with
children, but I can live with that.Thanks a lot for sharing.
Hmmm, interesting. I assumed that this would work recursivelybut obviously not. Maybe you need to do the recursive
david adams wrote:
Turned out to be one of those ID10T errors. I was installing a Windows
Service whose function is to monitor a Microsoft Message Queue. It helps to
name the MQ correctly lest your service will fail to start.
You should try the new suppress ID10T switch -- work wonders
Is this what you are looking for? Download and run dark against an
msi that has this functionality.
Dialog Id=ProgressForm Width=375 Height=287
Title=[ProductName] Modeless=yes
Control Id=NextButton Type=PushButton X=300 Y=261
Width=66 Height=18 Disabled=yes
John Ludlow wrote:
I ported your code to C++ and it does indeed work.
That is, it hides features. It doesn't seem to work for features
with children, but I can live with that. Thanks a lot for
sharing.
Hmmm, interesting. I assumed that this would work recursively but
obviously not.
Mike Dimmick wrote:
I'd take a guess that
PowerShell is somehow messing up the parsing of the : and giving the
two arguments "-cultures" "en-us", and that light's command-line parser
then interprets "en-us" as being a source file for it to process. It
then fails because it can't
Sigurd Stenersen wrote:
And there is no way to delay CostFinalize to just before the featuretree
dialog is displayed ?
No. Costing happens early in the UI sequence. MSI expects the UI to have
that information.
It IS possible to customize it from the outside using the command line to
set
OK, either my questions are getting easier
or Im starting to get the hang of this. I figured out that I need to
escape the brackets and now it works fine.
My follow-up question is how do I check an
XML file to see if an element already exists?
If the appSettings element is already
Hi all.
Im sure I already know the answer to some of these
questions, but I must ask. Is there a repository of user-submitted WiX UI
content? Are there any available templates of some of the more popular
dialogues that are used in MSI installers? Is there an unwritten spec to adhere
to?
Yes, I am aware of this problem, and I have been working some larger changes
that would make this problem go away among other things. I haven't made a
lot of progress lately however, so since it is being raised here I'll try to
get a fix in for this specific issue within the next week or so.
Frank Tse wrote:
I
am wondering if setup should fail in the first place when it
cannot put the DLL in GAC. i.e. Netfx extension that puts DLL in GAC
should
fail when it cannot put DLL in GAC.
MSI installs assemblies to the GAC by handing it off to the Fusion
engine. Fusion
Marshall Cai (Comtech GEMS) wrote:
One issue
Im
from which the extended group of MS HWSW. Currently, Im doing a
research work on nested MSI with WIX. Do anyone know how to implement
that with WIX.
From
the link
47 matches
Mail list logo
