Hello WiX users,
I've created custom action to load websites list from IIS.
View listBoxView;
DirectoryEntry iisRoot;
int order;
listBoxView = session.Database.OpenView("select * from ListBox");
iisRoot = new DirectoryEntry("IIS://localhost/W3SVC");
order = 1;
foreach (Director
Hi:
I'm creating an installer where I'm modifying the WixUI_InstallDir dialogue set.
I've copied the fragment from the file in the source containing the
WixUI_InstallDir dialog definition, and in my product.wxs I have:
I get the following when trying to compile using visual studio 2008:
Hi,
I've just upgraded to Visual Studio 2010 from 2008, so installed WiX 3.5
instead of WiX 3.0.
When I try and build my custom action project, I get the following error:
LINK : fatal error LNK1181: cannot open input file 'dutil.lib'
I couldn't find any obvious solutions to this from searching
On Sun, 26 Sep 2010 15:22:26 +0100
Mark Simonetti wrote:
> I've just upgraded to Visual Studio 2010 from 2008, so installed WiX
> 3.5 instead of WiX 3.0.
> When I try and build my custom action project, I get the following
> error: LINK : fatal error LNK1181: cannot open input file 'dutil.lib'
d
Okay thanks :-)
Mark.
On 26/09/2010 15:53, Bruce Cran wrote:
> On Sun, 26 Sep 2010 15:22:26 +0100
> Mark Simonetti wrote:
>
>> I've just upgraded to Visual Studio 2010 from 2008, so installed WiX
>> 3.5 instead of WiX 3.0.
>> When I try and build my custom action project, I get the following
>
Hi:
I've got the following component in a .wxs file:
It is included in a feature as follows:
On a 32-bit version of window xp sp3, the 64-bit component is still being
installed.
Anyone got any ideas why?
I only want
Hi:
I need to use the RegistrySearch element in a property. I need to look a key
who's default key has no default value (regedit show "value not set"). What
will the property be set to? I'll need to use this property in a launch
condition. Should I do this or could I use a custom action to set
On 26-Sep-10 13:39, Sean Farrow wrote:
> I need to use the RegistrySearch element in a property. I need to look a key
> who's default key has no default value (regedit show "value not set"). What
> will the property be set to?
Nothing. See the RegLocator doc.
--
sig://boB
http://joyofsetup.c
On 24-Sep-10 03:48, David Amey wrote:
> Thankyou for this, but it's not quite the solution I need. I need the
> option of the language selection, as the client needs different
> languages on different machines.
MSI doesn't support multi-lingual UI.
--
sig://boB
http://joyofsetup.com/
---
On 23-Sep-10 05:31, Pally Sandher wrote:
> In my defence Bob I wrote my patching code when I was using WiX 2.0 thus
> the only method available to me was the PatchWiz method. When I moved
> over to using WiX 3.0 I looked at the Pyro method as the idea of using
> purely WiX appealed but as time is
On 25-Sep-10 07:41, fiordean dacian wrote:
> Now back to my problem, can you see any problem in the log I posted below or
> is the fact that I'm using a UI and schedule MigrateFeatureStates which
> creates me problems?
The MigrateFeatureStates SDK doc describes its limitations, including:
The
On 26-Sep-10 10:07, Sean Farrow wrote:
> How do I go about solving this ,do I need to rename my dialog set?
Yes.
--
sig://boB
http://joyofsetup.com/
--
Start uncovering the many advantages of virtual appliances
and s
On 26-Sep-10 12:41, Sean Farrow wrote:
> I only want to create one install, as this is the one file that differs.
MSI doesn't support 64-bit components in a 32-bit package. You need two
packages.
--
sig://boB
http://joyofsetup.com/
On 24-Sep-10 15:55, Bruce Cran wrote:
> which is written using WiX 3.5 but I just get a permission denied error
> if I try and do a perUser installation which installs to
> ProgramFilesFolder - as I know I should do! As far as I know I can't
You need to set Package/@InstallPrivileges to elevate
On 24-Sep-10 19:36, John Fry wrote:
> as it gives: error LGHT0204 : ICE03: Invalid format string; Table:
> Environment, Column: Value, Key(s): OURPROD_TGT_PATH.GUID_HERE
What value ends up in the .msi?
You can fix the problem using built-in MSI properties, like
CommonFilesFolder.
--
sig://bo
On 24-Sep-10 08:02, Sean Farrow wrote:
> I am in the process of writing a custom action to run an executable, can I
> concatenate a property name with a string literal of my executable?
FOO[BAR]BAZ[#asdf.exe]
--
sig://boB
http://joyofsetup.com/
--
On 23-Sep-10 10:31, Mark Simonetti wrote:
> It doesn't seem to be working for some reason, whether the initial
> install has them turned off or on, I never seem to be able to change
> it.
Transitive component conditions are re-evaluated only during a
reinstall; a change operation doesn't trigge
On Sun, 26 Sep 2010 16:13:59 -0400
Bob Arnson wrote:
> You need to set Package/@InstallPrivileges to elevated (or leave it
> off). Otherwise, WiX marks the package for "real" per-user operation,
> which won't ask for elevation and can't write to Program Files.
>
I had hoped that would work, b
On 26-Sep-10 17:28, Bruce Cran wrote:
> I had hoped that would work, but it doesn't seem to. The combination of
> InstallPrivileges="elevated" and InstallScope="perUser" doesn't result
> in any elevation prompt (and the "Install" button in the MSI doesn't
> have a UAC shield).
InstallScope doesn
On Sun, 26 Sep 2010 17:44:51 -0400
Bob Arnson wrote:
> InstallScope doesn't support per-user, elevated packages. Just omit
> InstallPrivileges (defaults to elevated) and don't set ALLUSERS.
Thanks, that's one combination I hadn't thought of trying. When I
removed both InstallScope and InstallPr
Hi:
What is the best way of compiling 32/64 bit msi's from the same sorce. Is there
a property already available to check the platform, or should I set a property
on the platforms that are 64 bit in visual studio.
Cheers
Sean.
--
Hi:
I need to sequence a custom action before any launch conditions are checked,
what sequence is the best one to use. This custom action should run whenever
the msi is run.
Cheers
Sean.
--
Start uncovering the many advan
Hi,
We’ve built a custom DLL for our WiX-powered installer because our product
has a pretty complicated install sequence. Our custom DLL runs as a deferred
custom action since it modifies system files, etc.. The problem we’re facing
is that since our DLL does the heavy lifting of registering our
23 matches
Mail list logo
