I would be interested in a solution to this as well!
--
Edwin
-Original Message-
From: dschmitz [mailto:[EMAIL PROTECTED]
Sent: Monday, October 06, 2008 2:59 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Search Replace template parameters in SQL
Hello,
we have lots of
I noticed that the SourceForge downloads page is pointing to Wix 3.0.4318.0
rather than 3.0.4513.0 or 3.0.4603.0. I had downloaded 3.0.4513.0 before from
the SourceForge downloads page but it is no longer there. Is there some place I
can download that build?
--
Edwin
-Original
I've created a merge module that uses [PSDOMAINNAME], [PSUSERNAME], and
[PSPASSWORD] in an util:User/ element for the purposes of creating an
application pool. I noticed that the user is not getting set correctly and
discovered that the property names have the merge module package guid
I'm trying to schedule a custom action to execute before any other steps occur
during uninstall only:
InstallExecuteSequence
Custom Action=CACmdLine Before=RemoveRegistryValuesInstalled AND
NOT REINSTALL/Custom
Custom Action=CA After=CACmdLine Installed AND NOT
REINSTALL/Custom
I'm trying to execute a powershell script as custom action and I see the
powershell.exe process starts but then it appears to be doing nothing. Here's
an example:
Property Id=POWERSHELLEXE
RegistrySearch Id=POWERSHELLEXE Root=HKLM
-users@lists.sourceforge.net'
Cc: Castro, Edwin (Hillsboro)
Subject: Executing a PowerShell Script as Custom Action
Date: Tue, 25 Nov 2008 14:10:24 -0500
From: Castro, Edwin (Hillsboro) [EMAIL PROTECTED]
Subject: [WiX-users] Executing a PowerShell Script as Custom Action
I'm trying to execute
to Execute First Only
During Uninstall
Edwin,
To inspect the full sequence, just open up your msi package in orca
and look at the InstallExecuteSequence table.
~/Ali
From: Castro, Edwin (Hillsboro) [EMAIL PROTECTED]
I'm trying to schedule a custom action to execute before any other
steps
I've created a number of WiX projects in a Visual Studio 2008 solution and
would like to use T4 templates to reduce the repetition we see in our *.wxs
files. I've found that Visual Studio 2008 does not automatically hook up my
*.tt files as it does for C# projects. I've tried replicating the
Bob Arnson [mailto:b...@joyofsetup.com] wrote:
Castro, Edwin (Hillsboro) wrote:
I've created a number of WiX projects in a Visual Studio 2008
solution and would like to use T4 templates to reduce the repetition we
see in our *.wxs files. I've found that Visual Studio 2008 does
for T4 Templates in Visual
Studio 2008
Castro, Edwin (Hillsboro) wrote:
Do you know if the Visual Studio SDK mentions anything on DSL and
custom project types?
Sorry, no.
--
sig://boB
http://joyofsetup.com
Better tools for working with MSMQ would be very nice. I've found that
the MSMQ extension is very difficult to work with, particularly around
setting permissions.
--
Edwin
-Original Message-
From: Eitan Behar [mailto:ei...@baconao.net]
Sent: Monday, December 29, 2008 6:00 AM
To:
I'm also using v3.0.4805.0 and started experiencing these Internal MSBuild
Errors. I've noticed that building from the command line works fine while
building from within Visual Studio does not. I found these two emails on a
similar situation:
it working again in Visual Studio itself.
-Original Message-
From: Castro, Edwin (Hillsboro) [mailto:egcas...@checkfree.com]
Sent: Thursday, January 22, 2009 9:33 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX 3.0.4805.0: Internal MSBuild Errors
environment was like? Mine is a
quad Core I7 with 8gb of ram and a fast raptor drive... When I get the
solution from TFS, this is the only computer that has problems building
it... I am wondering if it has to do with the high-concurrency...
-Original Message-
From: Castro, Edwin (Hillsboro
I accomplished the same thing as follows:
Directory Id=TARGETDIR Name=SourceDir
?if $(var.Platform) = x86 ?
Directory Id=ProgramFilesFolder
Directory Id=INSTALLLOCATION Name=./
/Directory
?else?
Directory Id=ProgramFiles64Folder
Directory Id=INSTALLLOCATION Name=./
and ProgramFiles64Folder. With any luck I won't need to be
choosy anywhere else (we're depending on the build system to place files in the
right place).
--
Edwin
-Original Message-
From: Castro, Edwin (Hillsboro) [mailto:egcas...@checkfree.com]
Sent: Tuesday, January 27, 2009 8:11 PM
To: General
Do you need to handle upgrades? If so, how are you going to handle file
renames, deletions, etc?
I wrote my own utility (in C#) to rip through a directory and generate WiX
source (similarly to heat.exe) except that it specifies FileSource differently
so that I don't have to touch up the
Check that you are deploying all your dependencies. If your service depends on
3 assemblies and one of those depends on 2 other assemblies (for a total of 6
assemblies) and you forget to deploy just one of them, then the service will
fail to start because it can't load a dependent assembly.
--
What is the difference between !(bind.VariableName) and !(wix.VariableName)?
I've seen examples of !(wix.VariableName) usage in WixUI_Advanced.wxs but can't
find a reference in the documentation. My gut tells me they are two syntaxes
for referencing WixVariable values.
Assuming my gut is
I have a scenario where I have a fragment I want to repeat numerous times with
just a few parameters changed (for differences in names, GUIDs, etc). I don't
think WiX provides a template-like facility so I was wondering how people
manage similar scenarios.
Right now I'm debating whether I
Sounds like you might be missing a reference to WixUtilExtension.dll
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail
-Original Message-
How does the installer know what the customer has ordered?
To me this sounds like each database set is a feature that the customer can
choose to install. The feature for db1 would contain references to components
that represent the contents of db1.cab. You could partition your installer so
The Csc task expects ProjectReference items to resolve to projects whose output
is a .NET assembly.
Visual Studio solutions allow you to specify non-ProjectReference
dependencies.
I don't understand what you mean by traversal project.
Edwin G. Castro
Software Developer - Staff
Electronic
System.Version defines the following format:
major.minor[.build[.revision]]
We defined those as follows:
The product release defines major and minor numbers (static and changed
manually).
The build number is the CI build number (automatically increments by one every
build).
The revision
that, that wasn't really my question but it is nice to hear
other peoples approaches.
Neil
-Original Message-
From: Castro, Edwin (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: 12 March 2009 20:28
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users
I've seen many people report that they are running powershell custom actions
successfully but I can't seem to find any examples of how they do it. My goal
is to run powershell silently. I'm trying to do it as follows:
DirectoryRef Id=INSTALLDIR
Component Id=SampleScriptPS1 Guid=*
File
The documentation says that FeatureGroupRef is a valid child of FeatureRef. I
have the following:
FeatureGroupRef Id=FeatureGroup
Feature Id=ChildFeature1/
/FeatureGroup
FeatureRef Id=ParentFeature
FeatureGroupRef Id=FeatureGroup/
/FeatureRef
ParentFeature is defined in a different source
for Windows Installer XML toolset.
Subject: Re: [WiX-users] Executing PowerShell Silently Hangs Install
Castro, Edwin (Hillsboro) wrote:
I've seen many people report that they are running powershell custom
actions successfully but I can't seem to find any examples of how they
do it. My goal is to run
[mailto:b...@joyofsetup.com]
Sent: Saturday, March 14, 2009 10:25 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Can FeatureGroupRef be a child of FeatureRef?
Castro, Edwin (Hillsboro) wrote:
The documentation says that FeatureGroupRef is a valid child
Opened bug 2689061.
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Saturday, March 14, 2009 10:25 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Can FeatureGroupRef be a child of FeatureRef?
Castro, Edwin (Hillsboro
Try
Exec Command=pathto\heat.exe dir quot;Folderquot; -gg -sfrag
-template:module -out quot;heat.wxsquot;/
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this
Theoretically, devenv.exe will call msbuild under the covers. You can tell
msbuild to build your solution and tell it which configuration/platform you
want to build. Something like:
msbuild path\to\solution.sln /p:Configuration=Release /p:Platform=Mixed
Platforms /t:Build
Some more
First check that LocalPath is pointing to the correct location. Sometimes the
bug is sooo trivial we don't notice it. ;-)
SvnVersion/ expects svnversion.exe to live at $(ProgramFiles)\Subversion\bin.
If it doesn't live there, then specify ToolPath to the directory where it does
live. Example:
am doing it.
DefineConstantsDebug;ReleaseDir=..\ProgramName\bin\Release\;Subversio
nRevision=$(Revision)/DefineConstants
Any help is greatly appreciated.
Brian
2009/4/22 Castro, Edwin (Hillsboro) edwin.cas...@fiserv.com
First check that LocalPath is pointing to the correct location
DefineConstantsDebug;ReleaseDir=..\MYAPP\bin\Release\/DefineConstant
s
/PropertyGroup
/Project
2009/4/23 Castro, Edwin (Hillsboro) edwin.cas...@fiserv.com
My example depended on having the CollabNet distribution of
subversion.
Find out where svnversion.exe lives on your system.
I expect
-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail
-Original Message-
From: Castro, Edwin (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Thursday, April 23, 2009 9:08 AM
To: General discussion for Windows Installer XML toolset
36 matches
Mail list logo
