You can use the sql:SqlScript tags to execute sql scripts from with in
your Wix project. SQLCMD is used to deploy sql database projects, you can
have wix execute the command, though this is a fairly complex process and
may not achieve your objectives as in some cases it will drop tables.
Kind
Hi,
We are using wix to create our installer packages. We are not using any
custom UI dialog in our installer ( Basic msi installer)
We are creating an msi installer which supports the localization for few of
the languages. When we install the msi on specific language OS the installer
displaying
As far as I'm aware that text comes from Windows Installer and is not taken
from your MSI file. I
don't think there is anything to you can do about it. I'd love to know if I'm
wrong though.
Rob
On 10/12/2010 10:33, sreelatha polaki wrote:
Hi,
We are using wix to create our installer
Hi,
I am doing Wix 3.5 upgrade testing and I notice that the MSI I created
after upgrading my votive Wix 3.0 project to 3.5 alters the schema
codepage to 1252 even though I explicitly set it to 0.
This means that I can't make a patch as the msi codepages do not match.
After a bit of
Yes, I suck at wix. Thanks for pointing that out. Now, about my original
question? Any ideas?
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Friday, December 10, 2010 12:13 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users]
Scenario:
1. I have several (let's say 4) custom dialogs. The first dialog conatins a
list control so the installer can select the 'environment' (i.e., production,
test, qa, dev, etc.0. this list is populated dynamically by a custom action.
The custom action allows the developer (person
I had a thing like that a couple of months ago. Product/@Codepage would
be 1252 no matter what I set it to, even if setting it to something
totally different like 1256.
I opened a bug in the tracker and I think it got fixed. Which weekly are
you using? Have you tried it in Escrow 2?
PS I was
Hi,
I am indeed using the escrow 2 (2403) build, I also tried in wix 3.6.
I also notice that you don't even need to use anything in the
WixUIExtension just add a votive reference and it changes the codepage.
Dave
-Original Message-
From: Thom Leigh [mailto:t...@mondago.com]
Sent: 10
The file must be generated by WiX during build time.
-Original Message-
From: Jeremy Farrell [mailto:jfarr...@pillardata.com]
Sent: Thursday, December 09, 2010 7:42 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How do you fix this error? (id is too
So you've hard-coded the Product/@Codepage to 0, but when you add a
reference to votive, it ignores that and sets it to 1252 internally?
What if you hard-code it to another value? Like 1256? Same behavior?
You should probably see if this is reproducible and if so file a bug
report...
I think you'd mentioned before that it was during the compile, as
opposed to the link, which I suspect, too. You can certainly break those
down into two discreet steps to figure out which one it is. Assuming it
is the compile then it would be in one of the .wixobj files, since that
is what the
To me, it looks like it is because the filename is long.
$(var.Core.Data.DataManagement.Plugins.Client.TargetDir)XPT.Core.Data.DataManagement.Plugins.Client.pdb
The physical directory is this:
C:\XPertSeries\Source\XPJ-R7S3\bin\debug\plugins\platformclient
Did you know that your original post on December 6th didn't make it to
the mailing list? It's only in the reply to your own e-mail on the 9th
that made it so others could see your initial inquiry from the 6th. Just
thought you might find that interesting because you'd mentioned silence
on the
Thanks a lot for these details!
Taking your Manufacturer xsl as a baseline example, I tried to replace the
Name attribute in Product but really made no progress. I got this crappy
code to work, but would like something like this.
xsl:template match=packa...@name
xsl:attribute
That's Strange, I received the initial post as if it came from the mailing
list.
-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Friday, December 10, 2010 11:01 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How
1) Does vsixinstaller.exe require elevation (and are you running it from an
elevated commandline)?
2) Do you elevate before starting MSI during your install?
3) Does vsixinstaller.exe use/require access to your user profile? Does that
profile access include process environment variables? Those can
Thanks for digging into this further. The support e-mail for DIFx Tools
is difxt...@microsoft.com. I have received responses over the years from
different people, but never any resolution to my problems. If that
e-mail address is no longer valid, then I can give you the addresses of
the specific
Add xmlns:wix=http://schemas.microsoft.com/wix/2006/wi; in the root element of
your XSLT and change your template to:
xsl:template match=wix:packa...@name
xsl:attribute name=Name$(var.ProductName)/xsl:attribute
/xsl:template
-Original Message-
From: sangeeta1
What are you trying to do in change mode? Detect whenever the user adds
Feature_XYZ? Or detect anytime it is either added or stays?
It's hard to write conditions when you don't know the scenario.
-Original Message-
From: little.forest [mailto:little.for...@ymail.com]
Sent: Thursday,
Built-in Windows Installer can append or prepend values to MULTI_SZ during
install, and (I suppose) remove those specific values on uninstall. I don't
think it natively supports removing arbitrary values, though.
-Original Message-
From: sagar shinde [mailto:sagar.i...@gmail.com]
Sent:
Maybe this will explain what you are seeing:
http://blogs.msdn.com/b/heaths/archive/2006/10/25/how-windows-installer-uses
-languages.aspx
Blair
-Original Message-
From: Rob Hamflett [mailto:r...@snsys.com]
Sent: Friday, December 10, 2010 3:29 AM
To: wix-users@lists.sourceforge.net
The Wix schema does not let me add a attribute to Package though. I want
to assign a package Id to the msi.
xsl:template match=wix:Package
xsl:attribute name=Id$(var.PackageId)/xsl:attribute
/xsl:template
With you example, I am able to edit the Product name. thanks.
xsl:template
For #1: You could use the CopyFile/ element where your source directory is
as described here: http://msdn.microsoft.com/library/aa371857.aspx. However,
to combine this with #2, instead use this in creating your path to the file
you will copy directly.
For #2: you could try a FileSearch (see the
Thanks for your repply Blair.
I understood how to make this work:
1. Use FileSearch to locate the file.
2. If found use CopyFile to copy this file to install dir. If not found then
use Browse file dialog to locate the file.
However I am having difficulty in refering to this file which will be
xsl:template match=wix:Package Will match the Package element itself.
You'll need to copy the element, *then* add the attribute to the copied element.
xsl:template match=wix:Package
xsl:copy
xsl:apply-templates select=@*/
xsl:attribute name=Id$(var.PackageId)/xsl:attribute
The source .wxs file that Heat.exe generates, does not contain Package Id. I
was therefore thinking of passing a new Guid every time the tool is run. Is
there any way Heat.exe can set Package Id in the .wxs file?
Thanks for the list of reference books.
On Fri, Dec 10, 2010 at 2:01 PM, Edwin
Heat.exe doesn't need to set Package/@Id at all. Candle.exe will set
Package/@Id at compile-time to a new Guid if one is not specified in the .wxs
file. My recommendation is to not add your own Guid with a XSLT transform and
to let candle.exe perform it's default action concerning Package/@Id.
I figured it out. Following is the code if it could help some newbie like me
:-)
Property Id='FILEEXISTS'
DirectorySearch Id='DirSearch' Path='[SOURCEDIR]' Depth='0'
FileSearch Id='FileSearch' Name='NewFile.txt'/
/DirectorySearch
/Property
Component
Hi Blair,
Thanks for your reply.
We'd like to detect whenever the user adds the feature XYZ.
Basically, we have a component which is an Outlook plugin. During installation,
the user can choose install it or not. If the user doesn't install it in
initial
install, then she can add it in
Hello gapearce,
Can you please share the code on how to create the Custom fileopen dialog
and then using the selected file in further installation process.
Thanks so much.
--
View this message in context:
Seeing as how this seems to be a fundamental problem with DIFxApp not
handling all the upgrade possibilities well, I was curious to see how other
products do things and so I ripped apart some MSIs in Orca. I was looking
to see if DIFxApp was set up the same way (CustomAction table). I also
Where are you defining the files that are getting copied? I see CopyFile
elements in this component, but no File elements. Does the ScriptsLocation
directory already exist and have files in it? If so, you may try marking the
Component element with the KeyPath attribute.
-
Learn WiX with the
32 matches
Mail list logo
