You might find this an interesting read:
http://blog.deploymentengineering.com/2008/05/deployment-tools-foundation-dtf-custom.html
---
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
--
Msiexec is not a console application. It is a windows application. When msiexec
starts control is immediately passed back to PowerShell. This is the equivalent
of using the "start" command in a command prompt. This means that msiexec is
still executing when PowerShell executes the next command.
Hello,
I am trying to create database and table in SQL Server 2008 using scripts.
The script works fine when executed manually in Management studio. But fails
with above error "Error 26201. Error -2147467259: failed to create SQL
database" when executed from installer.
My target machine is Window
Thank you.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Michael_A [mailto:mcl...@fullarmor.com]
Sent: Friday, March 11, 2011 4:50 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Trac
This isn't a WiX question directly but hopefully someone will have some
experience they would be willing to share.
I am using PowerShell to run msiexec on a remote machine. Right after I zip up
the files that were installed. But PowerShell is too quick because by the time
I get to executing the
Just turn tracker off. /p:TrackFileAccess=false
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Friday, March 11, 2011 5:53 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Tracker.exe??
I tried linking and it gave me this
I tried linking and it gave me this error on Tracker.exe not finding a response
file. I was hoping that someone on this list has seen this error and as a
reasonable workaround. The first link had responses like:
Sometimes A/V has been known to interfere with build tools. Have you tried
exemptin
Try this
Go to VS2010 -> Team Explorer -> Builds -> EDIT BUILD DEFINITION -> PROCESS
-> ADVANCED -> MS BUILD ARGUMENTS and add "/p:TrackFileAccess=false" then
SAVE.
Kevin Burton wrote:
>
> I am getting a warning
>
> WixUI_Mondo.wxs
> WpfComponents.wxs
> Product.Generated.wxs
> Link:
>
*SIGH* Did you read any of the links that showed up in the search? ... Really,
I would expect more from a Senior Software Engineer.
I'm not a senior anything... but I know how to search and read.
If you can post additional information as to what you learned, what you tried,
and how it worked or
So what have I done wrong that causes this error?
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Friday, March 11, 2011 4:13 PM
To: G
One thing is that it looks like you're not allowing for the automatic
redirection of various things such as the registry when you run 32-bit things
on a 64-bit system. If your installer is 32-bit and you run it on a 64-bit
system, then references to 'SOFTWARE\Microsoft' will get silently redirec
http://lmgtfy.com/?q=wix+tracker.exe
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-
> From: Kevin Burton [mailto:kev...@
I am getting a warning
WixUI_Mondo.wxs
WpfComponents.wxs
Product.Generated.wxs
Link:
C:\Program Files\Windows Installer XML v3.5\bin\Light.exe -cultures:null -ext
"C:\Program Files\Windows Installer XML v3.5\bin\\WixNetFxExtension.dll" -ex
t "C:\Program Files\Windows Installer XML v3.
So cross-compile fails (trying to compile x64 on a x86 machine) but running x86
on an x64 platform works and 'Any CPU' fails. At least that has been my
experience.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
Hi Again,
I've just created a log of my installer and it seems that I've got some
of it work now but the last test just left me with a mangled install
that won't uninstall :(
According to the log both of these searches found their registry values,
which is confusing since using regedit I can o
It looks like the only difference is the fact that I am compiling on an x86
platform. Have you tried 'Any CPU'? When I specify 'Any CPU' the CA will not
run with the afore mentioned errors in the log.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@bu
Hi All,
I thought I was on the right track with this, but after some testing
it's not working as expected.
I've defined this in my installer:
VERSIONNT64
VERSIONNT
As sean said below he uses QuiteUninstallString but in the registry that
is the "path to the uninstall.exe" with
I think I've cracked it.
VERSIONNT64
VERSIONNT
On 10/03/2011 22:23, Sean Farrow wrote:
> Hi:
> On a 32-bit version of windows, your key would look like:
> "SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{413B7644-1F93-4890-BD40-AC540C29935B}_is1"
> I don't tend to use SilentU
Actually I had to specifically compile to x86 before it would work even though
the target machine was x64. If I specifically compiled to x64 I received a
warning on the build machine what I am compiling to something different than
the current machine but when it came to running on the target mac
Sorry the table I added @ the bottom did not get sent correctly. I reformatted
it below.
Hi - I would greatly appreciate any help in understanding the timing of when I
have access to the original or updated version of files installed during a
patch install, uninstall and rollback sequences of b
I've got an installer for a utility that includes a COM+ component. The
solution was originally created in VS2008 and targetted .NET 3.5. The
solution was 'upgraded' to VS2010 and .NET 4.0, and now the installation
fails ...
Here's a fragment for COM+ component & TLB [this was working fine until
I've got an installer for a utility that includes a COM+ component. The
solution was originally created in VS2008 and targetted .NET 3.5. The
solution was 'upgraded' to VS2010 and .NET 4.0, and now the installation
fails ...
Here's a fragment for COM+ component & TLB [this was working fine until
FYI: The "DLL" is a .NET assembly. The "CA.dll" is a native C++ assembly that
is responsible for setting up the .NET environment needed to run the .NET
"DLL". As you found out, you need the bitness of the "CA.dll" to match the
target machine.
Edwin G. Castro
Software Developer - Staff
Electroni
Hi - I would greatly appreciate any help in understanding the timing of when I
have access to the original or updated version of files installed during a
patch install, uninstall and rollback sequences of both.
The Install process seem fairly straight forward. I have availability of the
old fil
Hello WiX community,
I've got a requirement to change the name of the installed files based on
the user input. The initial thought was to use the property values, but it
turns out not to be supported. I've also read this: "
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-a-lt-P
Hi I'm having problems with creating an msi that works for different locals.
Below is an extract from the log file
I have created an msi for each language, changing the Language in the
Product element to 1033 and 1040
I can run both the 1033 and 1040 msi on the machine and they display the
correc
Am I asking this question in the wrong group? After downloading the
Wix source and pondering on this a bit further, instead of taking a list
of dependent dlls I believe it would be better to take a single/list of
fragments containing the harvested data of the dependent component.
Jacob
-Or
I am sorry I had inadvertently set the tag to the DLL *not* the CA.dll
so with the compile target of the CA specifically set to x86 (*not* Any CPU)
the CA is called correctly. Thank you.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
Along these same lines I tried building the CA project setting the target as
x64 just to see if this made a difference. I did get a different error message
but it still didn't work:
MSI (s) (60:B0) [08:07:23:200]: Doing action: CA_CheckCredentials
MSI (s) (60:B0) [08:07:23:200]: Note: 1: 2205 2:
I appear to be looking at the same problem. I was able to reproduce it by
hitting 'cancel' near the
end of an uninstall and letting it rollback. After that uninstallation failed.
Performing a repair
fixed things. Did you email the difx team at the email address Quinton
suggested, and if so
It is currently set to 'Any CPU'.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Michael Osmond [mailto:mosm...@baytech.com.au]
Sent: Thursday, March 10, 2011 8:49 PM
To: General discussion for Windows I
31 matches
Mail list logo
