One last thing .. using the "/t:rebuild" on the MSBuild of the WiX project
has alleviated the need to delete the WiX project and get the latest from
the source repository.
On Mon, Jul 27, 2009 at 12:06 PM, troy hostetter
wrote:
> Here are my results.
because all output files are up-to-date with
respect to the input files.
Hmm .. I guess that "Skipping target Compile" means the WiX preprocessing
never runs (just dawned on me) .. doh!
So, to conclude, I will be setting the environment variable to null at the
end of my build script, a
WiX project has a pre-build event as such (this is also set in my build
script prior to executing MSBuild on the WiX project):
set Install_Environment=local
I then try to reference this in my WiX code:
I get the following error message:
error CNDL
t be associated with a component.
>
> Thanks,
> Mike Carlson
>
> -Original Message-
> From: troy hostetter [mailto:troy.hostet...@gmail.com]
> Sent: Wednesday, July 01, 2009 11:54 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-us
FWIW .. I passed in the IP address of the existing web site .. the new WiX
looks like:
Still no go :( .. same error as below.
- Troy
On Wed, Jul 1, 2009 at 2:54 PM, troy hostetter wrote:
> Mike -
>
> Installed version 3.0.5419, built msi, and am now getting this err
e Carlson
>
> -----Original Message-
> From: troy hostetter [mailto:troy.hostet...@gmail.com]
> Sent: Wednesday, July 01, 2009 9:31 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] WriteMetabaseChanges: Error 0x80070057: failed to
&g
We are getting the following error and are not sure why. We have been
successful at creating virtual directories in several other environments
(development, integration, etc.), however the environment we are currently
deploying to is having issues :(
Action 14:41:11: StartMetabaseTransaction. Sta
Bob -
Just want to say thanks for your help .. y'all are doing great things!
- Troy
On Sat, Jun 6, 2009 at 6:16 PM, Bob Arnson wrote:
> troy hostetter wrote:
> > So .. if I understand this correctly .. Windows Installer 4.5 supports
> > execution of custom actions on patch
Thanks,
- Troy
On Tue, Jun 2, 2009 at 8:11 AM, Bob Arnson wrote:
> troy hostetter wrote:
> > Id="XC__kCEnterprise.Search.web.config.delete.1"
> > File="[KCENTERPRISE.ROOT.WEBDIR]web.config" Action="delete"
> On="uninstall&quo
executing on uninstall. Could this be a problem
with Custom Actions?
On Sun, May 24, 2009 at 10:14 AM, Bob Arnson wrote:
> troy hostetter wrote:
> > error PYRO0260 : Product '{1F6FE067-01BE-4D39-B880-0AEF3E4F84D0}': Table
> > 'CreateFolder' has a new row
We have successfully built and utilized a "MST" file when deploying our RTM
version of our product. A separate MST file is built for each of our
separate environments .. Dev, Integration, and Production. We use the
following command to pass in this transform file:
msiexec -i Product.msi -l *xv -
put says:
>
> Binder temporary directory located at
> 'C:\Users\hostette\AppData\Local\Temp\xmydgbq7'.
> Unbinder temporary directory located at
> 'C:\Users\hostette\AppData\Local\Temp\xmydgbq7'.
> Torch temporary directory located at
> 'C:\Users\host
> Verbose log file should show you what Components are being changed. My
> bet is that your 10 unchanged Components KeyPaths are not being updated.
>
> troy hostetter wrote:
> > I am attempting to patch an existing web.config file with new web.config
> > settings. When I execute
I am attempting to patch an existing web.config file with new web.config
settings. When I execute msiexec and pass in the msp file, the
"util:XmlConfig" patches are not being applied.
My Tools.v1.0.1.Patch.wxs file looks like:
*
http://schemas.microsoft.com/wix/2006/wi";>
I am having a hard time determining the best way to handle patching v1.0
with v1.n. I have all my wxs files built for v1.0, and would like to move
forward with v1.n. I have read the WiX doco, which explains the process of
building a patch "Using Purely WiX". This process seems to assume v1.n wil
Getting a type mismatch on this:
Win64="$(loc.Win64)"
Here's the error:
Error407The Component/@Win64 attribute's value, '$(loc.Win64)', is
not a legal yes/no value. The only legal values are 'no' and 'yes'.
- Troy
On Mon, Mar 16, 200
rrors:
Second configuration .. getting type mismatches:
Thanks.
- Troy
On Sat, Mar 14, 2009 at 1:20 PM, Bob Arnson wrote:
> troy hostetter wrote:
> > Are there any recommendations on how to easily
Hmm... Ran across
this<http://blogs.msdn.com/astebner/archive/2007/08/09/4317654.aspx>after
I fired off the email.
If anybody has other ideas, or links to them, please forward.
Thanks,
- Troy
On Fri, Mar 13, 2009 at 12:28 PM, troy hostetter
wrote:
> Are there any recommendations
Are there any recommendations on how to easily switch between x86 and x64
when building the MSI?
Would be nice to dynamically or quickly change these:
- Troy
--
Apps built with the Adobe(R) Flex(R) framework and Flex
Is there any way to get the directory in which the msi is executing from?
If we copy the MSI to c:\foo, i'd like to copy files to c:\foo without the
user having to specify this directory via .
I thought there might be an internal directory ID .. like CURRENTDIR .. or
something.
- Troy
---
I see there is a RegistrySearch, FileSearch, DirectorySearch, AppSearch ..
and even an IniFileSearch. Is there such a thing as XMLFileSearch?
I'd like to do some conditional processing based on XML. Any solutions out
there?
- Troy
I am wondering how to set these IIS using WiX .. I cannot find them in the
element?
- Troy
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Op
//www.artizan.com/
>
>
> ---- Original Message
> Subject: [WiX-users] Creating VirtualDir within existing WebDir
> From: troy hostetter
> To: wix-users@lists.sourceforge.net
> Date: 2/25/2009 2:33 PM
> > Any idea how to do this? What I want is to
Any idea how to do this? What I want is to create MyVirtualDir within an
existing WebDir called MyWebDir.
IIS looks like this:
MyWebSite
MyWebDir
MyVirtualDir
My current WiX configuration looks like this:
Would someone have an example of how to "subscribe to the feature selection
events on the feature tree and set a property when the appropriate feature
has been selected and reset that property when the feature is deselected."
or something similar? I am not familiar yet with subscribing to feature
This is my first post to the user group. I am having a problem getting a
custom dialog to conditionally appear after the CustomizeDlg, which is based
on the user selecting or not selecting a feature in the CustomizeDlg.
Here are my conditional statement(s) for CustomizeDlg:
WixUI_Ins
26 matches
Mail list logo
