> Is there a recommended way to install [COM registration]
> information into the 32-bit part of the registry from a 64-bit
> (Win64="yes") component?
We're now thinking of registering our COM server using RegistryValue
elements, where RegistryValue/@Key contains "Wow6432Node". Does anyone
know of
Figured it out
-downloaded Wix 3.0
-Wix 3.0 installed templates in Visual Studio 2008
-used these templates to create CA.dll in c#
-used regular Wix CA actions to call CA dll and dll entry point
-tested good
ty
--
View this message in context:
http://n2.nabble.com/wrapping-compiled-c-net-
Are there any "best practices" for managing a larger WiX project in
VS2008? I need to create four MSIs (32/64 bit versions of two releases,
differing only by configuration files.).
* 32-bit specific WiX project containing 32-bit libraries from
developers
* 64-bit specific WiX proje
Hi All,
I got this weird issue.
My installer creates a registry key in HKLM and stores the INSTALLDIR value. It
provides default INSTALLDIR, however user can change it and the changed value
gets stored in registry.
Installer also have Change option enabled that REINSTALL = ALL
All works f
Thanks for the response Bob,
If I set impersonation to No it tries to run the action using local sytem only
and custom action throws error.
> Date: Sat, 6 Mar 2010 10:47:18 -0500
> From: b...@joyofsetup.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] SSRS deployment using
On 05/03/2010 02:00, Bob Arnson wrote:
> On 3/4/2010 3:50 PM, Richard Fine wrote:
>
>> MSI (s) (48:34) [19:55:31:273]: Invoking remote custom action. DLL:
>> C:\Windows\Installer\MSIBFC7.tmp, Entrypoint: ExecXmlConfig
>>
>>
> What's after that line? There should be a bit of logging if it
I read the example from the wix tutorials on how to do custom actions that are
not a part of Wix.
The tutorial states to use a dll and gives an example in c. Problem is I can't
read c so I do not understand what is going on (vb.net and c# work for me).
I created a simple dll in c# to create
On 3/5/2010 1:05 PM, admiristra...@cox.net wrote:
> I was searching around for a solution to easily update my MSI version
> numbers with each build, but I couldn't find one. So I wrote this and now I
> don't have to remember. Thought I'd share...
>
Even easier method: Use binder variables to
On 3/5/2010 4:32 PM, Uma Harano wrote:
> Can I use the "Greater than equal to " operator for this?
Yes, for the simple case of "4" > "3" but all the operators in MSI are
ordinal comparisons, so "3.0.200" is not greater than "3.0.1000."
--
sig://boB
http://joyofsetup.com/
-
On 3/5/2010 6:08 PM, Sachin Dubey wrote:
> I have a WIX 3.0 installer that deploys SSRS reports using a differed C#
> custom actions.
>
> The impersonation it set to "yes".
>
Impersonated custom actions aren't elevated. If you need elevation, it
must be "no."
--
sig://boB
http://joyofsetup
On 3/5/2010 12:34 PM, admiristra...@cox.net wrote:
> I know we can configure a Launch Condition to check for the existence of
> another installed product before installing, but is there a way to enforce
> or at least warn the user if they later attempt to uninstall the
> prerequisite (especially if
On 3/5/2010 8:31 PM, Alec Taylor wrote:
> Unfortunately, cannot access that website: Parse error: parse error,
> unexpected $ in /w/d/d...@interware.hu/wix/st882/var/access.php on
> line 113
>
Works fine now.
--
sig://boB
http://joyofsetup.com/
-
I was using registry to store the properties from user, and it was working
fine on most of the machines, but one machine got a problem, it is not
getting any user input properties.
Machine A
Action 17:59:55: WriteRegistryValues. Writing system registry values
WriteRegistryValues: Key: \SOFTWARE\O
13 matches
Mail list logo
