I have an x86 screensaver that unfortunately needs to remain so at present
because it uses COM objects that are still x86. I can install this on an x64
system and the *.scr file runs OK, but doesn't show up as a screensaver
because it's in %sys32%\SysWow64. I can right-click on the *.scr file in
the advantage of being pretty precise as to the changes made.
Chris Mumford wrote:
I've got a customer asking me what files and registry values my installer
creates. I'm thinking of something like MakeMSI's installation
reporthttp://makemsi-manual.dennisbareis.com/sample.htm.
I understand
I've got a customer asking me what files and registry values my installer
creates. I'm thinking of something like MakeMSI's installation
reporthttp://makemsi-manual.dennisbareis.com/sample.htm.
I understand that a report like this isn't that valuable because of
conditional logic and differences
I think you want to use msizap.
On Thu, Jul 24, 2008 at 12:51 PM, Eric Latendresse
[EMAIL PROTECTED] wrote:
How can I manually un-install a setup? I get an error when I try to
remove my setup from Add\Remove programs.
Thanks,
Eric
I think that having examples in the documentation would help out immensely.
On Sat, Jul 12, 2008 at 9:12 AM, Rob Mensching [EMAIL PROTECTED]
wrote:
Uhh, yeah. You asked how to condition a custom action and that says
specifies the condition of the action. Am I missing something? Is there
I can't see anything obviously wrong here, but my suggestion is to create a
verbose log and see what the property values are:
msiexec /i setup.msi /l*vx Install.log
Also, if you aren't using it
Wilogutl.exehttp://msdn.microsoft.com/en-us/library/aa372811.aspxis
a nice tool to analyze the logs
to the end of all the primary key identifiers in
the MSI. The MSI SDK talks about this process in detail.
-Original Message-
From: [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] On Behalf Of Chris Mumford
Sent: Thursday, July 03, 2008 16:36
To: General discussion for Windows Installer
Hey Rob, could you elaborate on what you mean by that? Have you already
discussed this elsewhere?
On Thu, Jun 26, 2008 at 5:36 PM, Rob Mensching [EMAIL PROTECTED]
wrote:
Correct, .wixlibs won't help you there. Unfrotunately, that means you're
stuck fighting with the Modularization of
I just wanted to make sure I'm not doing thing the hard way here. I'm
creating an inatallation and I want my customers to be able to modify some
its many properties. From what I can see they have the following options:
1. Specify a property on the command line.
2. Use Orca.
3. Use a WiX
of a ProductVersion, so
there's no distinction between 3.0.0.0 and 3.0.0.1. Is that what you're
seeing?
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] On Behalf Of Chris Mumford
Sent: Monday, June 16, 2008 8:28 PM
To: General discussion for Windows
:) When you run the chm click on Using WiX in
Visual Studio in the first page that shows up. There's 6 topics on it.
Neil
From: [EMAIL PROTECTED] [
[EMAIL PROTECTED] On Behalf Of Chris Mumford [
[EMAIL PROTECTED]
Sent: Wednesday, June 18, 2008 9:52 PM
:
Chris,
I'm curious, why do you use this approach instead of the shipping
wix.targets build process that comes with WiX?
Neil
From: [EMAIL PROTECTED] [
[EMAIL PROTECTED] On Behalf Of Chris Mumford [
[EMAIL PROTECTED]
Sent: Tuesday, June 17, 2008 8:04 PM
no distinction between 3.0.0.0 and 3.0.0.1. Is that what you're
seeing?
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] On Behalf Of Chris Mumford
Sent: Monday, June 16, 2008 8:28 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX
You don't want to call MSBuild *from* WiX. Instead you want to mave MSBuild
call WiX. Attached is my MSBuild project file that calls candle.exe and
light.exe to build an MSI file.
You can see that I have the path to the WiX bin folder hard-coded (and my
machine is x64). So as an improvement you
I learned a few years back not to change my upgrade code, unfortunately a
little too late. The good news is that I only changed it once. My current
WiX source is:
Product Id=A390115B-BF30-4481-8F46-9615FEE3C5C5 Name=MyProduct
Language=1033 Version=$(var.Version) Manufacturer=MyCompany
And BTW thanks for mentioning the deployment engineering blog. I never came
across that, but just subscribed to it.
On Tue, Jun 10, 2008 at 7:02 PM, Christopher Painter [EMAIL PROTECTED]
wrote:
But you could write a bootstrapper that caches and tweaks the package based
on user input before
:12 PM, Chris Mumford [EMAIL PROTECTED]
wrote:
Hey Neil:
Thanks for responding. Sure, I do have other directories like:
Directory Id=ProgramFilesFolder
Directory Id=DesktopFolder
Directory Id=SystemFolder
Directory Id=CommonAppDataFolder Name=MyDataDir
Directory Id
PROTECTED] [
[EMAIL PROTECTED] On Behalf Of Chris Mumford [
[EMAIL PROTECTED]
Sent: Sunday, June 08, 2008 5:42 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Source vs. target
I'm ashamedly naive about a fairly core issue with WiX. Maybe you guys can
clear
bump.
On Sat, Jun 7, 2008 at 6:26 PM, Chris Mumford [EMAIL PROTECTED] wrote:
I have a requirement for the end user to be able to add files to my MSI
before they deploy it to their machines.
At present I wrote a program to use msi.dll to allow them to customize some
properties - it writes
I'm ashamedly naive about a fairly core issue with WiX. Maybe you guys can
clear this up for me. As I write my installer I've been thinking of the
source files as those that I am installing, and the target as where they
will be on the machine on which the install is being run.
So right away I'm
I have a requirement for the end user to be able to add files to my MSI
before they deploy it to their machines.
At present I wrote a program to use msi.dll to allow them to customize some
properties - it writes out a modified *.msi file as well as a *.mst
transform file.
I see some discussion
Can somebody help me figure out what I'm doing wrong here. I'm trying to
lookup a file path in the registry and then do a FileSearch to see if it
meets the minimum version I require. Here's my code:
Property Id=FLASH_FILE_PATH
RegistrySearch Id=FlashFilePath Root=HKCR Type=file
Hello again:
I'm looking for a little help integrating a merge module. I'm trying to
distribute the Adobe Flash player - and Adobe does distribute a merge
module. So I added a Merge tag inside a Directory and then added a
MergeRef into a Feature in my main installer.
Now I'm getting these
Hi again:
During install I need to start a program that I've just installed, and I
also need to kill it during uninstall/upgrade.
I believe that I can just add a custom action to start it, but what about to
stop it? Is there a non CA solution to this problem?
Thanks!
-Chris
(to insult that word too) is
gagging for trial and error (and shot deadlines)
Hope that helps a bit.
-Mark
--
*Von:* [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] *Im Auftrag von *Chris Mumford
*Gesendet:* Montag, 12. Mai 2008 06:13
*An:* wix-users
Hi Justin:
Even though your advice and comments to Dong are 100% correct I'm still
going easy on him. I've had many frustrating days with Windows
Installer/WiX. I would say that these are most surely issues with Windows
Installer's complexity and not WiX - however WiX's tendency to assume that
I read a blog posting titled What do I do with per-user data when I
uninstall?http://blogs.msdn.com/oldnewthing/archive/2007/09/17/4948130.aspx
this morning and have often asked myself the same question. What do you
experts think?
Hey there:
I have an installation layout like this:
Setup.msi
CommonFiles/
where CommonFiles contain user configurable files. When I run the installer
I want to copy all of the files in the CommonFiles directory which is beside
my MSI into the:
%ALLUSERSPROFILE%\Application
Hi everyone:
Believe it or not I've been trying to solve this problem for about
five hours so needless to say I would love some help here!
My product installs a service and a screensaver. Because of the
service (and maybe the screensaver) I'm making the installation
require admin privileges to
29 matches
Mail list logo
