On Tue, 2013-12-10 at 14:31 +, John Cooper wrote:
Options that work: 1) give the text file a versioned binary
CompanionFile;
Tried it--doesn't work in some strange way: if I install the product in
'Program Files' directory (used by default), the installer doesn't
overwrite text files
Nicolás,
Good point. In all three scenarios the feature comes up selected to install.
For Scenario 1 this is expected. (new install)
For Scenario 2 this is unexpected. (major upgrade install where feature was NOT
previously installed)
For Scenario 3 this is expected. (major upgrade install
I suspect it works for me because the chosen companion binary file has it's
AssemblyFileVersion incremented every build. If there isn't a build-to-build
difference, the companion file will compare as equal and nothing will happen
to the unversioned file that is it's companion.
File versioning
File versioning is really important. - this feels like the understatement of
the week. smile/
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Thursday, December 12, 2013 6:13 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] repair does
Oh the trees I could kill on that subject.
As much as I love TFS, I still can't believe that after 6 years there still
isn't any build in AssemblyInfo processing in the default build process
templates. I can only imagine that Microsoft figured they couldn't make
everyone happy so they
Ah, my mistake, I missed that you were using a companion file, and it that
case the status of the text file is controlled by the version of the binary
versioned companion.
Phil Wilson
On Thu, Dec 12, 2013 at 7:21 AM, John Cooper jocoo...@jackhenry.com wrote:
Regrettably, after seeing the
It's possible that the major upgrade is migrating feature states. This does
not seem to explain the issue, although migrating feature states seems to
be what you want to happen, and that wouldn't need a registry search to
detect previously installed features. However, migrating feature states is
Hi,
I have a Windows service (among other things) that I am installing during the
process of my WiX Installer. The installer was working great, but it started to
have issues at one point. I believe (not 100% on if I did it before or after
the errors happened) I had manually removed the
I have the following ICE errors and am not sure how to track down the root
cause or how to repair. Can someone explain how I can find the cause of
these errors and fix them?
I am trying to use the Crystal Reports 13.0.7 MSM file to deploy CR with my
project.
ICE Errors:
ICE03: Invalid registry
You'll need to look at your servicecontrol in the WiX and in the MSI file.
It looks like your service name is incorrect. There's no enough info in
your post to say anything useful. For example, is the service name a
property? Is it a service you are installing or a pre-existing one?
The message
It appears that I added vcredist merge modules in the upgrade that cause
the upgrade to be permachine install. Is there anyway to bundle vcredist
merge modules but still have a peruser install?
On Wed, Dec 11, 2013 at 7:54 AM, Phil Wilson phildgwil...@gmail.com wrote:
If you don't specify an
You'd need to use the vc_redist exe and install that first. That merge
module has an explicit ALLUSERS setting because it's intended to be per
machine, so you'd need to take it out and use the redist exe.
Phil Wilson
On Thu, Dec 12, 2013 at 10:58 AM, Happy Geek happygeek...@gmail.com wrote:
But that would need a bundle, since running vc_redist.exe as a custom
action is crazy. Can't you just install the CRT DLLs in the same
directory as the executables?
--
Nicolas
2013/12/12 Phil Wilson phildgwil...@gmail.com:
You'd need to use the vc_redist exe and install that first. That merge
Are there any examples on how to install vc_redist.exe from wix?
On Thu, Dec 12, 2013 at 11:12 AM, Phil Wilson phildgwil...@gmail.comwrote:
You'd need to use the vc_redist exe and install that first. That merge
module has an explicit ALLUSERS setting because it's intended to be per
machine,
I can install the CRT dlls locally but how do I make sure they get updated
when there is an update?
On Thu, Dec 12, 2013 at 11:21 AM, Nicolás Alvarez nicolas.alva...@gmail.com
wrote:
But that would need a bundle, since running vc_redist.exe as a custom
action is crazy. Can't you just install
Oh wow, I can't believe I missed that. I've been staring at the ServiceControl
for the longest time, checking the logs, researching and researching.. I was
grabbing the name of the service from an undefined location, but in the
ServiceInstall I had it named properly.
As soon as I read that the
Some of the runtime Dlls can be installed into the local application
directory, true, but details depend on which CRT versions. I wouldn't just
delete the ALLUSERS in the merge module because there's probably a bunch of
SXS stuff in there too. If the Dll is really private then just put it in
the
Hello all,
Ok, I finally have Pure WiX Patching working on my projects. I have a small
issue though.
Melting all of our RTM products takes about 35 minutes to complete. What I
have found is that if I zip up this collection of goodies and stick it on the
network share ONCE, I can copy it
This is a vcredist.wxs file I found somewhere recently which works well for
me. It installs both x86 and x64 vcredist if needed, or just comment out
what you don't need.
Please note that the code below is for installing vcredist v3.5 which I
needed for Crystal Reports so make sure you update the
Ah. I see there is a MajorUpgrade element in WiX now. That is not what I
meant to convey when stating major upgrade. A new something to check out
though.
In this case we are using the following:
Property Id=NEWERPRODUCTFOUND Secure=yes /
Property Id=PREVIOUSVERSIONSINSTALLED
I have the following in my wixproj file:
Target Name=SignBundleEngine
Exec Command=quot;C:\Program Files (x86)\Microsoft
SDKs\Windows\v7.1A\Bin\signtool.exequot; sign /f
quot;$(ProjectDir)*.pfxquot; /p * /d quot;Utilitiesquot; /tr
http://timestamp.comodoca.com/rfc3161 /v
What does the output of MSBuild look like when you build your bundle? Is
signtool being called? (If you can't see it in the logs, you may have to
increase the verbosity.)
For the MSI/CABS,
Target Name=SignCabs DependsOnTargets=UsesSignTool
Exec Command=quot;$(SignToolPath)quot; sign /t
Phil,
Not sure if you have hit on something here. Based on some reading on the
MajorUpgrade element and various readings about subtopics we ran across
something odd. According to Orca there is no MigrateFeatureStates action in
the InstallExecuteSequence table of the MSIs built in WiX
I have installed WiX Toolset 3.8 on my windows ,But I cannot find
wixstdba.dll 。
Because the bootstrapperApplication only have English Resource Now , I
wanna find wixstdba.dll and change the english string to chinese .
Thank you !!!
I need to do some change of the wix source code , But do not know exactly
how to rebuild it .
--
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how
Hi,
In The Windows Installer's documents, It mentioned that
the Windows Installer determines whether the component's key file is
already installed before attempting to install the files of any component.
If the installer finds a file with the same name as the component's key file
installed
Hi All,
I am creating registry entries as below in WIX source file:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='EnergySolutionsConfig' Name=Energy Solutions
International
Directory Id='PFWServiceFolder' Name='PFWService'
Directory Id='CONFIG' Name='config'
Hi All,
May be this is a trivial question to ask, but below is what i want to
achieve:
I am creating registry entries as below in WIX source file:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='EnergySolutionsConfig' Name=Energy Solutions
International
Directory
Sorry for the redundant post, just happened by typo...ignore this one.
Original Message
Subject:Registry key created
Date: Fri, 13 Dec 2013 11:10:41 +0530
From: Suvrajyoti Panda suvrajyo...@contata.co.in
To: General discussion about the WiX toolset.
Hi All,
I just saw this behaviour. My installer creates the following
:C:\Energy Solutions International\PFWService\config, if this path is
open and i run the uninstall from control panel, then the path
remains(C:\Energy Solutions International\PFWService\config) although
files under it is
How can I to include all files from source folder and deploy them into a
target folder during installation. I have multiple images in a folder and i
want all of them to be included in msi automatically rather than including
all of them separately using file element. I am able to include required
31 matches
Mail list logo
