The origin calculation is not accurate. Such as an installation of 100M, the
actual space taken would be 100.4M. So, I want to tell the user, if he just
have merely enough space to pass DiskSpaceCheck step, that he would fail.
The simplest way to do this, seems to be use ReserveCost table to add ex
As far as I can see from the source code, it won't fail if the
application pool (or another metabase key) with the same name already
exists. It'll just try to create one, and if there's an error, it'll
check for the presence of such key and continue with OK status if it is
there.
I might miss some
Thanks for ur replies.
i got it.
Final conclusion:-
if you have 2 or more features and you want some of them not to
install(automatically when installer runs) unless user wants to install all
the features in CustomizeDlg dialog or if he selects COMPLETE installation.
For this you can initially
I am new to WiX. Recently we migrated to WiX 3. I am in need to customize my
Installer UI. Most of the articles available on net points out to editing
the .wxs [e.g. WixUI_InstallDir.wxs and InstallDirDlg.wxs.] file present in
WiX source to achieve this. However I could not find the wxs files with
Hello,
I was just installing the x64 version of WiX and noticed the files are
identical as in x86. All binaries are "Any Cpu" assemblies. Can someone tell
me what (besides the installer) are the differences in the x64 release of
WiX?
Best regards,
Sebastian Brand
Instyler Setup - Cr
They are in the folder "src\ext\UIExtension\wixlib".
Neil
-Original Message-
From: karthik.shenoy [mailto:karthik.she...@robosoftin.com]
Sent: 30 June 2009 12:27
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Regarding WiX UI customization: Information needed
I am new to WiX.
I have a merge module WiX project
http://schemas.microsoft.com/wix/2006/wi";>
Hi all!
I am unable to create an installer that installs the merge modules for
MapInfo's MapXtreme 6.8.0. There are a total of 4 merge modules that I
need to install:
MIFonts_6.8.0.msm
MapInfoCoreEngine_6.8.0.msm
MapInfoDesktop_6.8.0.msm
MapInfoMXTConfig_6.8.0.msm
I can install MIFonts_6.8.0.msm
I have a scenario where I need to changed the value of a YesNoType attribute
based upon a property I specify. In particular, during our beta period, we
remove assemblies from the GAC. However, during release, we leak the
assemblies to the GAC. This is done by setting the Permanent attribute on a
c
Brian,
The error that you are referring to will occur any time the command string
doesn't start with IIS://
Here are some examples...
heat website -gg -g1 -sreg /LM/W3SVC/1 -out .wxs
heat website -gg -g1 -sreg /LM/W3SVC/1/ -out
.wxs
as opposed to
heat website -gg -g1 -sreg IIS://localhos
Try it lowercased: 'yes' and 'no', instead of 'Yes' and 'No'.
-- Yan
-Original Message-
From: jnewton [mailto:jonathan.new...@ni.com]
Sent: Tuesday, June 30, 2009 5:46 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Using Variables with YesNoType Attributes
I have a scenari
Yeah, I meant to put 'yes' or 'no' in the post, but it doesn't matter. The
wix compiler always says the value is invalid according to its datatype.
--
View this message in context:
http://n2.nabble.com/Using-Variables-with-YesNoType-Attributes-tp3182903p3183321.html
Sent from the wix-users mail
That smells like a bug to me. The validation code for Component/@Permanent
_probably_ validates the literal attribute value rather than expanding
preprocessor variables first and then validating. I've noticed this problem
with other attributes too. From a toolset architecture perspective, which
The x64 installer also installs the MSBuild target files into C:\Program
Files\MSBuild\Microsoft\WiX so if you do a command line build using MSBUILD.EXE
from the Framework64 directory it works.
>-Original Message-
>From: Sebastian Brand (Instyler Software)
>[mailto:wix+us...@instyler.com
I was under the impression that the C++ custom actions are also built as 64-bit
DLLs. Is that not the case?
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-
Doh! Yes, the CA's have x64 versions too. The x64 version will also get the
dutil_*_x64.lib files as well.
>-Original Message-
>From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
>Sent: Tuesday, June 30, 2009 9:44 AM
>To: General discussion for Windows Installer XML tools
The x64 CA's also come with the x86 version of WiX. I believe the only
difference between the x86 and x64 releases of WiX is the MSBuild difference
mentioned below.
Also, to be clear, while some of the custom actions are also built as 64-bit
DLLs, others are not, and support 64-bit scenarios th
sorry for the repost.
Lian Jiang hijacked my thread and it got buried so here I go again.
Any ideas anyone?
--
I rigged one of my MSIs to fail immediately after IntallInitialize (a
deferred CA that with impersonate="Yes" is rigged to return an
I receive this error for each of the MergeModules my install projects
reference. I have been unable to find any information as to what the cause of
this could be. Does anyone have any suggestions as to what this might be?
Error 391 The target "GetResolvedReferencePaths" does not exist in
Howdy gang,
On my Windows Server 2008 x64 box, I've got Visual Studio 2010 beta 1
installed and tried to open a project which was barking because:
"...Installer.wixproj' cannot be opened because its project type
(.wixproj) is not supported by this version of the application."
Well, I (think I) kno
You have to convert the project by hand.
Basically what I did was create another project, and then I believe you can
simply copy the other files in. Once you have done one, you can diff the old
and the new, there are only a few minor changes between them.
-Original Message-
From: Erik
Hi,
I have some conditions in my msi, like the following,
But I need to run these conditions only if a certain parameter is set to
'true'. (i.e. msiexec /i installer.msi MYFLAG=true)
Are there boolean parameters, or do I need to treat 'true' and 'false'
valuse as strings?
Thanks,
Sandun
Thanks for all the replies.
My problem is that our tool is calling the WiX compiler, binder and linker
directly, without light.exe - light.exe is 32-bit only, probably because
winterop.dll (interop to Windows CabBuilder) is 32-bit only. Now calling the
WiX binder directly from our 64-bit tool, i
23 matches
Mail list logo
