Thanks Bob for this info.
===
Bhave
Bob Arnson-6 wrote:
>
> BhaveshG wrote:
>> I tried having Installer_Help.mht as binary id and using it with the
>> custom
>> action modified as below but somehow the value of HelpRef is not
>> reflected
>> and ShelExec gives an error with "Could not find 'He
BhaveshG wrote:
> I tried having Installer_Help.mht as binary id and using it with the custom
> action modified as below but somehow the value of HelpRef is not reflected
> and ShelExec gives an error with "Could not find 'HelpRef'"
>
MSI doesn't automatically extract "companion" files from the
John Vottero wrote:
> I believe that a major upgrade is essentially an uninstall of the old
> version followed by an install of the new version.
>
It depends on the scheduling of RemoveExistingProducts. If it's early,
then the new product is installed (bumping up ref counts) and then the
ol
Mike Dimmick wrote:
I think that's a doc bug - everywhere else it refers to 'nulls' with respect
to REG_MULTI_SZ it means [~], which is what Aaron is seeing.
Could be -- I'm allergic to REG_MULTI_SZ.
Does Windows Installer consider _ to be an uppercase character? Would
SQL_PROTOCOL be cons
On Tue, 19 Jun 2007, Dale Quigg <[EMAIL PROTECTED]> wrote:
> I'm new to Ant, so I didn't know that I needed to have my command
> invocation like this;
>
> dir="${iis_install.dir}">
>
>
...
>
> Instead of this, which does *NOT* work (one can no
You've hit a bug in heat.exe. Can you try dropping the .pdb file next to the
tools and running the case again to get a more detailed stack trace then open a
bug?
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pierson Lee
(Volt)
Sent: Tuesday, June 19, 2007 3:28 PM
To: wix-users
Hmm, that's kinda' weird. Have you tried using any diff'ing tools to see what
bytes are different? Maybe something obvious will jump out.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Don Tasanasanta
Sent: Tuesday, June 19, 2007 3:30 PM
To: wix-users@lists.sourceforge.net
Subje
I know I'm probably too late with this info...but if you have VS 2005 SP1, your
C++ dependency that you created with VS bootstrapper is not being installed
correctly. Update your
C:\Program Files\Microsoft Visual Studio
8\SDK\v2.0\Bootstrapper\Packages\vcredist_x86\product.xml
file to change thi
No bootstrapper involved. I can apparently make redistributable NSIS
files and just have another NSIS file run it silently. Which works just
fine. Also, no need to remember guids or the rest of that weird esoteric
stuff that windows installer seems to favor. And if I *really* need a
MSI for some un
Hi Sunghwa,
The value is stored in
I use "301" to ensure that customers have the MSI 3.01 engine. The 3.x
MSI engine has significant improvements that help patching.
Dale
Date: Tue, 19 Jun 2007 15:17:27 -0700
From: Sunghwa Jin <[EMAIL PROTECTED]>
Subject: [WiX-users] ICE66: Complete
The ability to install side-by-side assemblies (either .NET or Win32) was
added in Windows Installer 2.0. You should ensure that the user isn't trying
to install your package using an older version of Windows Installer by
setting the package schema to a high enough level.
You do this by setting
Ignore this. I figured out:
should be supplied.
From: Sunghwa Jin
Sent: Tuesday, June 19, 2007 3:17 PM
To: 'WiX-users@lists.sourceforge.net'
Subject: ICE66: Complete functionality of the MsiAssembly table is only
available with Windows Installer version 1.5. Your schema is 100.
Hi all,
I'm g
Is this a file you're installing? If so, the FileKey should be set to the Id
(not the filename) of the File element that installs the EXE.
Windows Installer should be coping with paths with spaces in here - it's
hardly a rare requirement considering that probably 99% of packages install
to "[drive
Is there any "WiX" explanation as to why the same code compiled and
packaged on two identical build machines would produce 9 meg msi's that
are just 3k different in size?
-
This SF.net email is sponsored by DB2 Express
Downlo
I'm getting the following error message when trying to create a .wxs file using
heat. I started trying to get the whole directory but I located the file that
its having a problem on and I'm trying to determine why I continue to get the
error message on even just using heat on that specific file.
OK, you misunderstood me, or I didn't explain it well.
What you need to do to satisfy the ICE is to add a RegistryKey to the
Component and set that as the KeyPath. Unfortunately you will have to do
this in the merge module that you're merging. If you can't fix the merge
module you'll need to suppr
Hi all,
I'm getting this error after I switch to WiX v3 when running Light.exe. Can
someone give me any clue about this warning? How can I solve this issue? Light
version is 3.0.2712.0:
warning LGHT1076 : ICE66: Complete functionality of the MsiAssembly table is
only available with Windows In
I think that's a doc bug - everywhere else it refers to 'nulls' with respect
to REG_MULTI_SZ it means [~], which is what Aaron is seeing.
I suspect a sequencing problem.
Does Windows Installer consider _ to be an uppercase character? Would
SQL_PROTOCOL be considered a public property or not? I'd
You need to pass the extensions on the candle command line if you intend to
use extended schemas.
--
Mike Dimmick
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dale Quigg
Sent: 19 June 2007 21:11
To: wix-users@lists.sourceforge.net
Subject: [WiX-users]
Sorry to answer my own post.
I'm new to Ant, so I didn't know that I needed to have my command
invocation like this;
Instead of this, which d
Hi,
I'm trying to build my WiX project using Apache Ant.
When I run my candle.exe and light.exe commands in a "plain" DOS command
(no WiX directories in path) the build is successful. The commands I
use are;
C:\PathTo\candle.exe MyProject.wxs
C:\PathTo\light.exe MyProject.wixobj
Hi,
I am using the below code to open a file on the button click event.
I am using ShelExec.exe as binary id to open the .mht file. Currently I am
having the Installer_Help.mht file along with the msi (installer) file which
I would not like to do (deliver two files).
I tried having
I believe that a major upgrade is essentially an uninstall of the old
version followed by an install of the new version.
I *think* you can get the effect you want by sequencing RemoveShortcuts
after CreateShortcuts but, I don't know what side effects you have to
watch out for.
> -Original
Certainly there are better places for configuration data. The advantage to
command-line options is that you can edit them without starting the
application, so to keep that benefit, I'd have to provide a separate
configuration tool. I'm not opposed to doing that later this week, but
having shortcuts
Cool! Thanks Mike. That works just the way I wanted it to.
From: Mike Dimmick [mailto:[EMAIL PROTECTED]
Sent: Monday, June 18, 2007 3:02 PM
To: Robert Priest; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Changed Installation Path
Use the [#filekey] syntax, where filekey is t
Beyond what Richard suggests below, you'll have to write a block of custom code
to do the migration of user data. Possible but mostly annoying.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Tuesday, June 19, 2007 10:02 AM
To:
I think my question would be why the user is forced into a (somewhat
unfriendly) specification of command line parameters as opposed to a
friendlier scenario using (for example) a configuration file, or a
configuration interface that stores things somewhere appropriate.
You may want to take a clos
A root value of -1 means use HKCU for a per-user install and HKLM for a
per-machine. If you're missing some registry entries from HKLM maybe
they're actually in HKCU.
Phil Wilson
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Albert
Tuulas
S
I have a Wix installer that includes something like this:
After installation, my users frequently add command-line flags to the
shortcut. When they upgrade to a new version, their shortcuts are
overwritten, losing the command-line flags
Maybe add "'s?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Harm-Jan
Zwinderman
Sent: Tuesday, June 19, 2007 3:42 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Question about CustomAction
Dear All,
I am trying to use a CustomAction in m
I doubt it. Raymond Chen (from the Windows Shell) rails on those registry keys
all the time. The correct way (from my reading of his blog) is to use
SHGetKnownFolderPath(). The Windows Installer has a built in way to do that,
just use the "PersonalFolder" standard directory. Didn't someone s
Yesterday I posted a question asking how to write to the "My Documents"
folder. Well after some experimentation I came up with this.
...
This compiles and runs without warning. Is this considered the correc
Dear All,
I am trying to use a CustomAction in my installer.
The CustomAction looks like this:
The CustomAction is called in the InstallExecuteSequence as:
1
When running the installer, the product is installed. However at the end
of the installation process I do get an error message:
There i
You’ll need a CustomAction, but probably only the really simple Type 51 (e.g.
Property set). Take a look at SystemLanguageID property from the MSI SDK and
you might condition your Type 51 CustomAction.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Palmer
Sent: Tuesday, Ju
Switching to forward slashes seems very strange on a Windows system. Many
people have found an easy way to make older tools that don't correctly handle
trailing backslashes is to put a dot on the end of the string.
"[ProgramFilesFolder]."
That gets me, "C:\Program Files\." which will be treate
35 matches
Mail list logo
