conversely does not need to) write to the
> registry (or anywhere else, for that matter), which is one part of what
> makes self registration non-repeatable and unstable. By using heat to
> harvest registry data, you simply move the self-registration step up from
> the actual installa
Yes, heat and tallow ran on win7 x64.
Are there any written rules one must follow when trying to gather
registry information? Must the machine be 32-bit, etc...? These are
32-bit c++ dlls.
Thanks,
Jon
On Tue, Oct 5, 2010 at 10:10 PM, Blair wrote:
> You don't say if the XP is 32 or 64 bit. You
When I use heat.exe v3, or tallow.exe to gather registry information
on XP, I get the following data:
When I use heat.exe v3, or tallow.exe to gather registry information
on Win7 x64, I get the following data:
Is there a reason for the missing ProxyStubClassId entry on Win7 x64?
Thank
My apologies. There is a mallow for WiX v3 located at:
http://www.x2systems.com/files/mallow_v3.zip
On Tue, Nov 24, 2009 at 9:31 AM, Jon W wrote:
> Is there a way to incrementally update a .wxs file with newly added
> files when using WiX v3? I could use heat.exe to re-read the
>
Is there a way to incrementally update a .wxs file with newly added
files when using WiX v3? I could use heat.exe to re-read the
directory contents to get the new files, but this changes all of the
previously existing file guids.
I was hoping for something like mallow in WiX v2 that had this opti
On Wed, Jan 28, 2009 at 8:35 PM, Bob Arnson wrote:
> Jon W wrote:
>> Has anybody succeeded at creating a transform that adds files?
>>
>
> That's a patch.
So, a patch is an acceptable way to install add-on products? Sounds a
bit unorthodox.
>> Should I create
I have an existing product that I need to break out into a few
individual products due to the large size.
As such, I would like to have:
Core.msi - The core product needed by other products
Add_On1
Add_On2
The bootstrapper would contain and install Core.msi, then download and
install one o
What are you using for a bootstrapper? I've been looking at the wix
mailing list, and elsewhere, and it appears as though everybody uses
something different.
For example, setupbld, msbuild, 3rd party software, homegrown, etc...
As a C++ app, I don't need any .net runtime libs, and would like the
t; Don't know if you can avoid it. All I can do is confirm that the behavior is
> exactly as expected. The CustomAction that does the slow scan is very, very
> unfortunate.
>
> -Original Message-
> From: Jon W [mailto:[EMAIL PROTECTED]
> Sent: Monday, October 27, 2008 15:22
I am installing the Visual Studio 2008 (vc9) runtime libs by
incorporating the vc9 mergemodule into my msi. The problem is as
follows... If a user has multiple side-by-side installations and
wants to uninstall an installation, then the msiexec process takes
minutes when evaluating whether it can
>
> 2. I'm quite certain that we'll declare WiX v3 stable (Production) before
> end of year 2009.
>
> Note: I know of a great many teams at Microsoft that have shipped on WiX v3
> their products (for example, Office 2007 & VS 2008).
Why is there a need for WiX to sit for another 1.5 years in b
Would you be able to list some of the PUBLIC properties that would be
propagated and not needed/wanted? It would be nice to know what may
cause issues, and why. If the properties aren't used and don't affect
the certain installers, then setting EnableUserControl=1 may work well
for some developer
Regarding the Vista installation issue of public properties not being
passed when the registry/domain settings are set to:
HKLM and HKCU Software\Policies\Microsoft\Windows\Installer
"AlwaysInstallElevated" (DWORD) to 1
Which of the following property settings is preferred?
or, add publi
> > Does anybody know how to force the installer to keep its specified
> > font size and not the user's font size?
>
> I sincerely hope you don't fine any such solution. I would never accept a
> program to override my UI choices. After all, I'm the one running my computer
> and deciding what pref
s.
>
> --
> Mike Dimmick
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Jon W
> Sent: 11 May 2007 18:22
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] fixed font size in installer windows
>
> Hi A
Hi All.
Is it possible to have a fixed font size for text within the installer
windows that are not clobbered by the user's font settings?
I already specify a font size, but certain user settings make the text
get truncated.
Thanks,
Jon
To automatically generate guids with tallow, use the "-gg" option that
is hidden.
i.e.
tallow -gg -s My.dll
On 5/11/07, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>
> More likely that my memory is fuzzy. I thought GUID generation only got
> added in Heat, but I've been wrong plenty of ti
I'm using Wix2.0 (4820) and the output produced by tallow -reg is
causing bad behavior when installing.
regcap.exe my.exe
tallow -reg my.reg
This produces the output:
But, when installing the log file shows that the values are being
written, then overwritten with empty valu
Hi All.
Should each registry entry be it's own component, or should it just be
part of a single component from which the "keypath" is the file that
contains the registy entries?
I would like the add/remove programs repair to fix any registry
entries that have been altered. Is there a benefit, or
Is this what you are looking for? Download and run dark against an
msi that has this functionality.
.
.
.
On 10/8/06, Alex Mendes da Costa <[EMAIL PROTECTED]> wrote:
> Thanks for suggesting th
> > The patching scenario is as follows:
> >
> > The product 1.0 is released.
> >
> > The patch 1.01.msp is released and built against 1.0.
> >
> > Another patch is needed, 1.02.msp. This patch is built against 1.0 so it
> > would include all of the changes since the original release. (The plan i
21 matches
Mail list logo
