Hello,
My setup uses a slightly modified WixUI_FeatureTree and contains features
which must be installed into different directories, some of which must be
selected by the user.
The problem is in the Change mode - the user cannot change default
directories for features which he/she wants to
Hello WiX community,
According to the MSI documentation, if 'NeverOverwrite' bit is set, the
installer does not install or reinstall the component if a key path file
or a key path registry entry for the component already exists. What
about components, which refer to the parent directory as a key
Hello,
What are the advantages of using util:InternetShortcut over:
a) IniFile creating .url file
b) .url File
?
I create one link in the Start menu using IniFile, because
util:InternetShortcut makes my setup 150 kB bigger, which is half of the
size of my whole package.
Thanks,
Piotr
Hi,
I want to convert many .reg files to .wxs files.
Is there an utility like heat ?
thanks,
Akihiro Shibuta.
--
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization
A quick look with a hex editor into my MSI reveals that this table is 50 kB
or so. I'd be happy to drop it if it's optional, preferably with a WiX
option. End users won't read Descriptions anyway, why are they so long
then?
Piotr
Blair os...@live.com wrote:
Besides what is available on MSDN
I think you need to keep this table to ensure others your app was ICE
validated, I remember this was part of the Designed for Windows
requirement or so.
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Blog: www.sebastianbrand.com
-Original Message-
Use tallow.exe from the WiX v2.0 toolset. You can then process the .wxs
files you output with WiXCop.exe in WiX v3.0 to update the XML in the
.wxs files from the v2.0 schema to the v3.0 schema.
Unfortunately that functionality was never replicated in heat.exe even
though it is the tallow.exe
Ok, I dropped this table with Orca and the MSI is just 19kB smaller which
is no big deal (however nice for open source software where you don't care
about certification).
Could you please explain This table is not shipped with the installer
database from the MSDN article linked below?
Thanks,
I asked a very similar question in September last year on this list. See
- http://n2.nabble.com/util-InternetShortcut-td838589.html for my
question Bob Arnson's reply.
More info on util:InternetShortcut on Bob A's blog at -
http://www.joyofsetup.com/2008/03/18/new-wix-feature-internet-shortcuts/
Remove the Condition elements in the code you pasted.
That will however enable the Browse button for all Features regardless
of installation status. To selectively enable it for Features which
haven't been installed yet and disable it for those which have you'll
have to modify the inner text of
Yes, util:InternetShortcut adds 150kB WixCA to the Binary table.
File Id=Website.url Name=Website.url Source=Website.url / seems to
work just as well as IniFile and the MSI is 0.5kB smaller. ;) You just
need to generate the Component Guid, because * doesn't work.
Piotr
Pally Sandher
Use a LaunchCondition in your MSI to detect for .NET 3.5 SP1 and deny
installation if it's not present. See
http://wix.sourceforge.net/manual-wix3/check_for_dotnet.htm
Also the following page may be of use to you if you're trying to create
a bootstrapper to install .NET 3.5 SP1 before running
Not unless you can re-write the standard error messages thrown by error
codes in Windows Installer (I'm guessing you don't work for the Windows
Installer team at Microsoft so that'd be a no). See error code 1633 on
http://msdn.microsoft.com/en-us/library/aa368542.aspx
Note that error codes are
i want to make single msi-file both to install or upgrade my application. i'm
using different product codes and single update code for all versions and i
store installation path in the registry.
running the installation i want to check the registry for my records
presence and if i find
No, don't try it with the option. It converts the warning into an error.
-Original Message-
From: Anurag Pahwa [mailto:apa...@microsoft.com]
Sent: Tuesday, December 01, 2009 6:40 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Pyro error
If the
From a functionality point-of-view, the table is not considered part of the
installation database (it is ignored if present by the routines involved in
installation maintenance of your product). However, many administrators
depend on guidance from the ICE tests and other tests which often depend
MSDN explicitly says that the keypaths required for this flag are files and
registry entries. When they are explicit they only guarantee the behavior
within the scope they describe. Since you are using a directory as the
keypath (and not a file) I assume the flag is being ignored, but you would
The warning most likely comes from the C:\ part of C:\MyDefaultDir\. Not
all Windows platforms have a C: drive. You may want to find a different
way to compute a default location for new installations.
-Original Message-
From: pushist1y [mailto:mister.p...@gmail.com]
Sent: Wednesday,
C:\MyDefaultDir\ is only a default value, in usual case i'm getting actual
value from registry.
--
/callvote set1v1 q3tourney2
--
View this message in context:
http://n2.nabble.com/setting-default-INSTALLDIR-tp4100396p4100949.html
Sent from the wix-users mailing list archive at Nabble.com.
You wrote: That worked pretty fine and the default installation path was
set to the path found in registry. But i'm getting compilator warnings for
that.
I responded: The warning is caused by your default value, not by what may or
may not already be in the registry or your pattern (which is
So MSDN is wrong when it says This table is not shipped with the
installer database? In that case I assume either that it's intending to
say something other than what it says, or it's presuming the use of a
particular toolset which strips the table. As far as WIX is concerned
though, this table is
Is it possible to log something to the installer log file from the XML
definition?
Thanks,
slide
--
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
I've been having an issue with my WiX patch which I haven't been able to find
any information for. The company I work for wants to give users the freedom
to install our product in a directory of their choice. We've given the
installer a default directory which can be changed at install time by
I ended up figuring this out on my own, it looks like the installer became
corrupted somehow so rebuilding the patch from scratch corrected the issue.
Not sure what caused the corruption though.
Big Jim.
--
View this message in context:
I am new to WiX. I have an example script working but need some help. In
one of the dialogs (I didn't write), there is a pushbutton that gets a SQL
path. The code for the button is below. How would I either force the button
to be pushed when entering the dialog or break up these commands into a
Please forgive me for the off-topic question but I figured somebody here would
know where I should look for an answer.
I was asked today if there was any way to add entries to Add/Remove Programs
*without* using a MSI. Is this possible?
Edwin G. Castro
Software Developer - Staff
Electronic
I have a wix installer which collects some of its content files from
installed program-files.
For example, we use NLog, and the installer collects the DLL from the
NLog install location.
We minimize configuration by searching the registry for the location
where NLog is installed, then using
Which XML file are you referring to, and what do you want to log that comes
from that file?
Off the top of my head I don't know of anything specific, but the answers to
these questions will go a long way to getting you an answer.
-Original Message-
From: Slide
That looks to me like an MSBuild question. I'm assuming that MSBuild 3.5
turns off registry redirection when reading registry keys to populate
properties based on your experience, but I haven't searched MSDN to see if
they describe 32/64-bit behaviors.
-Original Message-
From: Adam
Are your patches MSP files performing either small updates or minor
upgrades? If so, the patch application won't let you patch anywhere other
than the currently installed location since the keypath of the components
can't be changed without a major upgrade.
-Original Message-
From: XorPtr
MSDN documents this (a very little bit). Search for uninstall registry
key.
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, December 02, 2009 2:00 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users]
Sorry, I meant my Product.wxs (or any other wix xml source). Generally I
would just like to have something printed to the log if I did:
msiexec /i myinstaller.msi /l* install.log
I would like to do something like this:
Component Guid=SOME-GUID-HERE
Log Level=Info Message=Installing some
In my installer I install 3rd party software like MS .net 3.5 (dotnetfx35).
I have request to show progress in my pure Windows Installer while dotnetfx
is installed. Of course it has its own progress bar, but my installer still
shows static screen Prepare to install. During ExecuteSequence of
Thanks for the pointer. That page looks like it has enough information for my
colleague.
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
Unfortunately, not possible with those restrictions.
On Wed, Dec 2, 2009 at 7:11 PM, Igor Lemsky igor.lem...@gmail.com wrote:
In my installer I install 3rd party software like MS .net 3.5 (dotnetfx35).
I have request to show progress in my pure Windows Installer while dotnetfx
is installed.
Check out the MsiLogging property in the MSI SDK.
On Wed, Dec 2, 2009 at 6:09 PM, Slide slide.o@gmail.com wrote:
Sorry, I meant my Product.wxs (or any other wix xml source). Generally I
would just like to have something printed to the log if I did:
msiexec /i myinstaller.msi /l*
No but I've been working up to it. I'm staring down Burn right now. There
have been some pretty large changes in the project that have taken a while
to solidify. I wasn't talking about it in case things didn't happen (anyone
remember the WiX toolset shipping in VS then not? Yeah, me too.). I'm
Why not use the WixIisExtension. It will correctly support upgrade, patching
and rollback which your script below won't. smile/
On Mon, Nov 30, 2009 at 7:46 AM, Chris Carlson ccarl...@npr.org wrote:
I need to create a tree of virtual directories in IIS. The root of the
tree will refer to
38 is correct now (32 is an old incorrect value). The easiest way to solve
this problem is to use the EnsureTable element for the Extension table. The
WiX toolset will then use its definition (which is correct) for the column
before the Merge Module is merged and fix the error.
On Mon, Nov 30,
Can you please ensure a bug is open so this issue can be fixed? Thanks.
On Mon, Nov 30, 2009 at 10:54 AM, John Vottero jvott...@mvpsi.com wrote:
When specifying Priority=0 on the NativeImage extension, the installation
properly executes an ngen command with no /queue qualifier and the native
Your assembly is not loading. There could be a myriad of reasons causing
that. You'll need to debug the assembly loading issue first. Searching the
internet should give you the tools to debug assembly load failures.
On Tue, Dec 1, 2009 at 2:53 AM, MYFLEX shrinuen...@gmail.com wrote:
we have
Hmm, this line is very confusing to me:
CustomAction Id=Run_CustomAction.DDD8E6B5_8ADA_481F_B19D_55E2FFFAE621
Property=CustomAction.DDD8E6B5_8ADA_481F_B19D_55E2FFFAE621
Error=Merge Module Custom Action Failed Return=check/
I don't know what that would do. Maybe it will try to set the value of a
Was this ever resolved? Are you really getting an error message talking
about patching while using torch?
On Fri, Nov 20, 2009 at 12:46 AM, Stefan Pavlik stefan.pav...@gmail.comwrote:
Hi all
I have problem that is described on:
Did this ever get resolved?
On Fri, Nov 20, 2009 at 1:01 PM, Sharat Janapareddy
sharat.janapare...@microsoft.com wrote:
We made some changes to the MSI installer that was released this year and
we are releasing the SP soon. One of those changes include adding support to
uninstall the
Update the AssemblyFileVersion is the only way I know.
On Mon, Nov 23, 2009 at 11:13 AM, Mike Dion md...@vertical.com wrote:
I have an application which needs to install new bits for
Interop.FOOBARLib.DLL to the GAC. The problem is that the version
number is the same as the old version and
The MSI log file usually says what file causes the reboot.
On Tue, Nov 24, 2009 at 3:46 PM, Tony Juricic tjuri...@tradestation.comwrote:
I have verbose log and this is all the extra info that I find about the
cause of the reboot:
MSI (s) (4C:E8) [18:33:27:219]: RESTART MANAGER: Did detect
Hi,
I am facing issues when migrating the managed code from x86 to x64 platform. I
have a WIX project to create a MSI which will be executed through Bootstrapper.
On x86 Platform, files get copied in Program Files as per the Project.wxs
file. But if the same MSI is installed on x64 Platform
You present a database of how you wish the world to be configured for your
installation. Windows Installer takes that database and creates a script
from it. That script first analyzes which components need what (to be
installed, upgraded, repaired, removed) and then a script is written by
checking
Look for 1603 and 1903 INFO-type messages. You may need to add the x
along with the rest of v* or voicewarmup (depending on how you are
specifying the things to log) to get them but somewhere it will log telling
you exactly which files are causing the reboot.
So either voicewarmupx or v*x.
You build one MSI for 32-bit platforms (they can't install into 64-bit
locations) and another MSI for 64-bit platforms (which cannot be opened on
32-bit platforms). It is a limitation of Windows Installer.
-Original Message-
From: Vishwajit Walke [mailto:vishwajit.wa...@matrikon.com]
Thanks,
Indeed there was a problem with that line, and with the others. It looks
like WIX does not know how to look into a merge module created with
InstallShield to see what is in there so the custom action always
failed. I had to point the custom action to a binary file that is
created at
The older technology (the one used by Windows Installer) is called PatchAPI
(patchapi.h) and the newer one (not used by Windows Installer) is called
MSDelta (msdelta.h)
Both are described in this paper:
http://msdn.microsoft.com/library/bb417345.aspx. You can see the clear
advantages of MSDelta
Are you referring to WiX-contrib? (http://wixcontrib.codeplex.com/)
I'm sure contributions are welcome.
-Original Message-
From: Dominique Louis [mailto:dominique.lo...@amxeurope.com]
Sent: Thursday, November 19, 2009 8:18 AM
To: General discussion for Windows Installer XML toolset.
Was this ever addressed?
-Original Message-
From: Jason Jibben [mailto:jason_jib...@starkey.com]
Sent: Wednesday, November 18, 2009 8:46 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] SQL Script sequencing/committing issues
Hello WiX-Users,
I've been working on an
I haven't seen any more traffic on this, but if it is still an issue, I
noticed that if AppSearch runs in InstallUISequence it is suppressed in
InstallExecuteSequence, so any properties you are using that aren't UI-only
should probably be marked Secure as well. Also, AppSearch properties
should
55 matches
Mail list logo