Just had a quick skim over it, and at the bottom of part 2 your link to part 3
actually points to
part 2 again. Following the link to part 3 gives a Requested page not found
error.
Rob
Rennie Petersen wrote:
Julie,
Thanks for the Wiki.
To all interested:
I've published the first
Hello
Yea, I agree that in the Internet we have plenty amount of rollback examples.
But these examples show how to rolback INSTALATION process. And it is clear for
me. This point is also described in the link that you received. But I need to
rollback a custom action during UNinstallation
On 4/24/07, Scott Sam [EMAIL PROTECTED] wrote:
This is what I do. Basically make a shortcut to internet explorer and
pass the web address as the argument. I do it this way so that it
always opens another instance of ie when you use the shortcut instead of
opening it the current window.
Almost all of the WiX toolset CustomActions have rollback. If they support
rollback that means they've done it (at least considered it) for both install
and uninstall passes.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anton Tkachev
Sent: Wednesday, April 25, 2007 1:05 AM
Hi,
I am seeing appverifier break in WixCa.dll during action
ExecServiceConfig
00bbf8d8 7c85079b ntdll!DbgBreakPoint
[d:\srvrtm\base\ntos\rtl\i386\debug2.asm @ 42]
00bbf8e8 7c872212 ntdll!RtlpPageHeapStop+0x72
[d:\srvrtm\base\ntdll\verifier.c @ 2232]
00bbf964 7c873305
(moving conversation to wix-devs)
Ahh, yes, I see it now. Nasty trick I played on myself with the typedefs.
*phScript =
reinterpret_castWCA_CASCRIPT_HANDLE(MemAlloc(sizeof(WCA_CASCRIPT_HANDLE),
TRUE));
Should be:
*phScript =
On Tue, 24 Apr 2007 21:36:03 -0700, Bob Arnson wrote:
Bob,
If a user chose another browser as default -- and some 10 percent
have, according to some reports -- an installer should respect
that. To do otherwise probably borders on rude. OK, it crosses the
line to rude.
Some other reports,
Hi
When I build my installer using WiX 2.0 and include the Crystal Reports
for .NET 2.0 Merge Module, the installer throws error 2228. I've created
a package which didn't include anything except the Crystal msm and the
problem still occurred.
I've reduced it down as much as possible, and
DEXK JAHN, GXbor wrote:
Forcing IE in any way in an installation (unless you do it for a
company-internal setup where you know for sure what the default
browsers are) is not downright rude, it has already been reached the
level of being counter-productive. I can only speak for myself, but I
Two things stand out.
1) You custom action sequencing is wrong. Review the WiX tutorial and the
MSI docs on execution sequencing. The files you’re trying to use ARE NOT
installed until after a great number of actions already take place.
2) I’ve never tried to execute msiexec
So running the VBScript outside of the MSI works, and I'd expect it to work
inside the MSI. I have no control over building the other MSI's as that is
done by a build server, and I'd prefer not to have control over them.
Packaging the MSI's and installing the MSI's to some location works fine.
I
Nathan Lee wrote:
Running the VBScript outside of the MSI works, and I'd expect it to work
inside the MSI.
Nope. As others have already observed the sequencing is probably just
plain wrong (the MSI's may not exist on the disk at the time you try to
install them). Even if that were not the
Robert Randall wrote:
2) I’ve never tried to execute msiexec from a script inside of an
MSI package. There may be some other caveats with this. Perhaps others
on the list know more.
As far as I know it's impossible, as nested installs don't work.
Tony
Will doing a deferred execution of my CA work in my situation? My
understanding is that I can't set a property in a deferred custom
action, all I can do is read the property CustomActionData
If this is the case, my only hope seems to be to set the environment
variable in the custom action, which
It trying to harvest some COM registration information from a couple of
COM servers, one a DLL and one an EXE. I'm trying to use heat, and it
seems to work for the DLL but not completely for the EXE.
For the DLL I get a TypeLib element containing an AppId containing Class
elements, and the
Tom Quarendon wrote:
It trying to harvest some COM registration information from a couple of
COM servers, one a DLL and one an EXE.
Heat (and Tallow before it) can't harvest registry information from
out-of-proc COM servers -- the technique it uses works only for in-proc
servers.
Since
[EMAIL PROTECTED] wrote:
I need my Environment element to use the 8.3 path for INSTALLDIR, and my
CA was trying to set Property with this value. I'm not sure it would
even be possible to order the sequence in a way that the property would
ever exist when the Environment element was processed.
Anton Tkachev wrote:
Yea, I agree that in the Internet we have plenty amount of rollback
examples. But these examples show how to rolback INSTALATION process.
And it is clear for me. This point is also described in the link that
you received. But I need to rollback a custom action during
Mark Rendle wrote:
When I build my installer using WiX 2.0 and include the Crystal
Reports for .NET 2.0 Merge Module, the installer throws error 2228.
I've created a package which didn't include anything except the
Crystal msm and the problem still occurred.
Their merge module is
Hi,
I need to write different values to the registry depening on which
feature(s) has been chosen. I figured id use a [property] for the
RegistryValue entry. However, im wondering how could i find out which
feature has been chosen (through Custom Actions) ? Im pretty sure this is
really simple,
hi,
i have a problem when trying to have two media elements so defined.
Package
InstallerVersion='300' /
Media Id='1' /
Media Id='2' Cabinet='embedded.cab' EmbedCab='yes' /
the first media must be non-compressed and external to the installer,
the second must be embedded.
Heat converts the registry information it gathers into strongly-typed
WiX authoring. Take a look at
src\ext\UtilExtension\wixext\UtilFinalizeHarvesterMutator.cs for where
that particular magic happens.
I found that bit shortly after I posted. Thanks though.
If they're components you're
I think all you want is a pair of components with the required registry
values you want in each feature... the installation will choose which
registry value to write automatically.
Regards,
Gareth
--
View this message in context:
My question about where to install samples digressed to the following
question, for which I didn't get a clear answer. If anyone feels like
clarifying further on the proper way to do this, I'd appreciate it.
I have two components that each install a shortcut into a sub-folder of
To compy with users' prefered browsers, i find it easier to simply make the
shortcut (*.url) file and install it to the ProgramMenuFolder as a file.
For translations, you can localise the name of the file and so how it
appears in the shortcut list, but not the rollover description... so for
Quite. I wrote one a while back, something like this...
Dialog Id=ShortcutsDlg Width=376 Height=266
Title=$(loc.DIALOG_GENERIC_Title) NoMinimize=yes
Control Id=BannerBitmap Type=Bitmap X=0 Y=0 Width=376
Height=45 TabSkip=no Text=DlgBanner /
Control Id=Title Type=Text X=15 Y=6
While the dialog works, I'd much prefer some kind of list box of the
ProgramMenu rather than a browse control that enables users to dump their
shortcuts in some inappropriate locations... actually, anyone want to
suggest how to go about such an improvement to the above code?
Thanks,
Gareth
--
The InstallPrivileges attribute is indeed set to elevated. I never
actually figured out what behioural differences there were on the strength
of this attribute though...
--
View this message in context:
http://www.nabble.com/UAC-Prompt-Required-tf3637831.html#a10184850
Sent from the wix-users
Actually, that doesnt work, it complains about duplicate registry values
On 4/25/07, Gareth at Serif [EMAIL PROTECTED] wrote:
I think all you want is a pair of components with the required registry
values you want in each feature... the installation will choose which
registry value to write
So try this: An immediate CA after CostFinalize uses [!fileId] to get
the short path, chops off the filename, and sets another property to
just the directory, which you then use in an Environment element. Worth
a shot.
I think I've found an acceptable solution by creating the INSTALL dir
folder
Carl,
If I understand correctly, you're using a single registry item, and need
it to have a different value based on which feature(s) are installed.
I suspect what you probably want is to use the feature installation
state and/or feature action state property (e.g [FeatureKey] and
In my application, there's thousands of files, and some of them have the
same file name. I try to compile /link my project and shows the following
error:
Error 1 Item has already been added. Key in dictionary:
'pagetable15rightR.png' Key being added: 'pagetable15rightR.png'.
Their names
In my application, there's thousands of files, and some of them have the
same file name. I try to compile /link my project and shows the following
error:
Error 1 Item has already been added. Key in dictionary:
'pagetable15rightR.png' Key being added: 'pagetable15rightR.png'.
Their names
I ended up doing appriximately the same. I modified slightly BrowseDlg with
custom action written in C,
to validate selected shortcuts localtion. But still, it does not look good
enough for production software.
I saw Windows Installer setups where it was done quite nicely. I just wonder
how?
Thanks Mike! The problem was that I needed to make it a deferred action. I
had to do some reading and experimenting on that today, but I understand now
what was happening and why.
I'm working on demo-izing the reduced WiX installer I used while working on
this. I'll put it here:
Are the files declared in the same Component?
They should not be. Files for different folders should be declared in
separate Components.
Rennie
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of jrcolons
Sent: 25. april 2007 20:59
To:
Rob,
Thanks for looking.
Following the link to part 3 gives a Requested page not found error.
Yes, as I said yesterday only the first two pages were uploaded.
Now the first four pages are uploaded.
http://www.merlinia.com/mdt/WiXTutorial.msl
And page five is minimal, so I'd appreciate it if
I feel like I'm missing something here. Two things actually.
First, regarding rollback:
I want have a custom action in my installation that modifies the system in
some way that can't be handled another way.
The documentation Rollback Custom Actions implies that I need to schedule
a rollback
Light lays out your files on disk as you've specified in the
Directory/@SourceName attributes. If you've not set SourceName, the name
specified in the @Name attribute is used. If you want the source folder to
be the same as the parent directories source folder, set SourceName to ..
Note that the
Is there any way to write a message to the install log from a custom
action?
Chris Rowland* Software Engineer * SunGard * Data Management Solutions *
1194 Oak Valley Drive, Suite 100 * Ann Arbor, MI 48108 * Tel
734.332.4423 * Fax 734.332.4440 *
http://www.sungard.com/datamanagementsolutions
If you are writing a C++ custom action, then the WcaLog function in
wcautil will write to the install log or show you how to do it yourself.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent:
I've lost track of the original requirement here but.
If you want to know afterwards (in your app) which features from your
product were installed (and I assume you know their names) why not just
call MsiGetFeatureState (or equivalent)?
Phil Wilson
::MsiProcessMessage() or WcaProcessMessage() if you're using wcautil.lib to
hide some of the trickier parts of the MSI API for CustomActions.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Wednesday, April 25, 2007 1:08 PM
To:
Note huge caveat that ::MsiProcessMessage() doesn't work from DoAction
so if your CA is triggered by a button that will not work for logging.
Not sure how you're supposed to log from these, I have not found a
solution, perhaps someone else has
Haven't used WcaProcessMessage so I can't say if
Kevin Dente wrote:
I accomplished this by spawing the aspnet_regiis tool to switch the
framework version of the site. This involves a couple of steps:
Find the path to the tool:
Property Id=FRAMEWORKBASEPATH
RegistrySearch Id=FindFrameworkDir Root=HKLM
My projects has three options in the Setup dialog. Typical with
InstallLevel 3, Admin with InstallLevel 1, and the Custom option
which takes it to the Custom Setup dialog with InstallLevel 3 as the
default.
This all works fine, but I've run into trouble trying to modify the
installation by
Hello.
Stumbled across WiX today and knocked together a vanilla msi after
following the quick start in the help and am pretty impressed with what
I have seen.
However, I want to enhance what I have and check for the presence of the
.net framework sdk or the distributable version installed on the
Correct, as you note, you cannot log from a DoAction launched CA.
WcaProcessMessage is just a wrapper around MsiProcessMessage() that mostly adds
handling for cancel. WcaLog() is a wrapper around WcaProcessMessage() that
adds the concept of logging levels inside your own code and is used by
Other way around. The boostrapper contains your .msi.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gourlay, Colin
Sent: Wednesday, April 25, 2007 4:03 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Net Framework Check And Download
Hello.
Thanks. I will give this a try.
Colin
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Mensching
Sent: 26 April 2007 00:07
To: Gourlay, Colin ; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Net Framework Check And Download
Other way
Anthony Wieser wrote:
The documentation Rollback Custom Actions implies that I need to schedule
a rollback custom action before my deferred custom action, but also includes
this paragraph:
Commit CAs are dangerous in that they run only when rollback is enabled.
Avoid them wherever
Igor Maslov wrote:
It looks like a such common task, I wonder why WiX does not provide
specialized dialog for that.
Because you're the first to ask. So it's not that common at all.
--
sig://boB
http://bobs.org
-
Gareth at Serif wrote:
The InstallPrivileges attribute is indeed set to elevated. I never
actually figured out what behioural differences there were on the strength
of this attribute though...
MSI should elevate as soon as it starts the execute sequence. As always,
a verbose log is
jrcolons wrote:
In my application, there's thousands of files, and some of them have the
same file name. I try to compile /link my project and shows the following
error:
You can have many files with the same name but their ids must be unique
per package. If you use Heat to generate
Geoff Finger wrote:
This all works fine, but I've run into trouble trying to modify the
installation by running the msi file again later.
Install level is only effective during initial installation. It's not
used during maintenence mode. Your best bet is to organize your feature
tree to make
Is there a discussion or an article on what approach to take to develop
installer GUI.
If I'm not mistaken, I can see three ways of doing this:
1. Write Win32 application that will display all dialogs and collect all the
configuration data , and then call MSI passing this configuration.
2. It
56 matches
Mail list logo
