There may be some confusion here over the term "registration". Nothing in those
log entries is about COM registration, which I suspect is the issue. If those
OCX files need registering for COM then they need their COM registration
extracted (Heat.exe) and the corresponding WiX wxs file registry
Hi Rob,
Yes, the components are installed, because after the Client-Only install the
files are there and some registry data about them is also present. Take file
PVUOM.OCX for example, the file name appears under and only under the following
keys in the Registry.
HKEY_LOCAL_MACHINE\SOFTWARE\Mi
We've talked about this many times. The tricky part is storing the values
and handling uninstall, repair, rollback and all that. Today, my pattern
uses registry keys in Components to handle all the work... generating
Components with registry keys and putting them in Features would be tricky
(if you
Dan, sounds like a good thing to add to the documentation. Can you open a
bug in WiX v3.6?
PS: Glad the WiX toolset is working for you. Success stories are appreciated
as much as bug reports.
On Fri, Jul 8, 2011 at 4:26 AM, Daniel Madill wrote:
> I find the Action attribute values confusing as
Managed
http://wix.sourceforge.net/manual-wix3/authoring_bundle_application.htm
Meaning, you write a custom BootstrapperApplication using .NET (managed);
rather than using a standard one like
"WixStandardBootstrapperApplication.RtfLicense" (native, non-managed) or
writing a native, non-manage
Hi,
is there an max. for a file size? I got an file which is 2,17 GB big.
I got WIX v3.6.1629.0.
Christoph
--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive reco
I find the Action attribute values confusing as well. It didn't help that all
the examples I looked at used "createAndRemoveOnUninstall" even though that
generally isn't necessary. I would actually have found it much clearer to use
"createAndRemoveOnUninstall" and "createAndRemoveAllOnUninstall"
> We would never do something as silly as REQUIRE a native application
to install the .NET
> Framework just to use the WiX toolset's bootstrapper, Burn.
Well, I did not think so, but the first response through me off. The
answer told me it was use by Burn and that I was off the beaten path.
Imagi
One day someone should implement a @Persist on the property element, it could
even have ="yes" or ="encrypted".
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 08 July 2011 09:59
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-u
As you guessed, if you don't store and retrieve property values during
installation, they will be set to defaults during maintenance. The repair
probably fails because it's trying to log on the service using the defaults.
You'll need to save the values entered by the user.
http://robmensching.com/
Thanks
I should have tested before asking. It does work. Because of the action
attribute of the RegistryKey element I thought that I have to do
something explicitly to get the registry value removed on uninstall.
Regards
Val
On 07/07/2011 23:20, Rob Mensching wrote:
> How are you adding the re
11 matches
Mail list logo
