Hello,
Ive spent the last two days getting familiar with
WiX, the windows installer, and going through the great tutorial on WiX (http://www.tramontana.co.hu/wix/).
I especially liked the article posted a year ago
To be perfectly clear, you are trying to bypass a feature that was put in
place to protect users. I don't work with drivers and don't really know a
whole lot about them, in general, but I don't think you'll get a lot of
support trying to hack around the protection. The whole thing sounds pretty
Yeah, that scenario just doesnt work right. The problem is that Assemblies
going to the GAC arent committed until the very end of the install. That
means your InstallUtil calls (assuming InstallUtil can reach into the GAC,
Ive never tried) have to come after InstallFinalize. That means that
Rob,We're having issues with our mail server at work here so I don't know if you received this or not so I'm going to send to you again. I moved my email off my work account and only my personal mail so i know the messages get through.
Sorry if you received it twice. Below is my answer to your
Rob,We're having issues with our mail server at work here so I don't know if you received this or not so I'm going to send to you again. I moved my email off my work account and only my personal mail so i know the messages get through.
Sorry if you received it twice. Below is my answer to your
There is no public APIs to adjust driver
signing policy from the application.
Even though there are some hacks for that,
it is a tempering for operating systems and highly discouraged.
The only right way to achieve your goal is
to get WHQL certification.
WiX 3.0 has a very different method of customizing the dialogs than WiX 2.0
which is so far undocumented. It's (hopefully) much more simple.
Basically, just grab a sequence file from the sources that is similar to
what you want (like WixUI_Mondo.wxs) and put that in your sources and modify
it to
What are you trying to do overall?
Using feature conditions in a components condition is a little awkward
usually features directly determine if a component will be installed.
Derek
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam
Sent: Wednesday,
I am trying to run a batch file post install. In my Custom
Action I specify the location of the batch file using the FileKey attribute. I
then want to pass a parameter (file system location) into the batch file, so I
use the ExeCommand attribute. When I hard code this parameter, everything
Hello.
My installation package consists of MSI-file and set of directory with
additional files. Those files are used by type 1 custom action (DLL file
stored in a Binary table stream). Since these directory is required, in
MSI there is a property that checks for the directory existence (via
Here is my problem everyone. I have a msi that
installs several files into the gac. I DO NOT create a shadow copy of
these files on the file system until my property called CREATESHADOW has a
value of 1. These assemblies have installers in them that I need to
call. (I know managed
It would take some work to rebuild our wixlibs, but we plan to
rebuild them anyway when moving to 3.0 to take advantage of the embedded
localization information. So, no problem here without wixlib backwards-compatibility.
Regards,
Martin
From:
[EMAIL PROTECTED]
When we moved over to MSI we had to deal with existing InstallShield installs.
I got round the
problem by looking in the registry for the key InstallShield writes under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
using a RegistrySearch. I then used the set property
John Hidey wrote:
Here is my problem everyone. I have a msi that
installs several files into the gac. I DO NOT create a shadow copy of
these files on the file system until my property called CREATESHADOW
has a
value of 1. These assemblies have installers in them that I need to
I need to write out to a config file what
features are being installed, so that the program that update/creates the
database knows what database to create/update if any at all.
From: Derek Cicerone
[mailto:[EMAIL PROTECTED]
Sent: Thursday, July 27, 2006 6:12
PM
To: Scott Sam;
Hello.
I have two Components installed into different directories. And these
Components include the same file, so the same file appears in two
different directories.
I have authored an MSM with two Component elements under different
Directory elements. Those Component elements include File
This is actually the primary reason why I started the thread about WiX and
support for installation of Windows instrumentation features. I too use
Enterprise Library and have suffered with some of these very issues.
All EL does is install some event sources, performance counters and WMI
First off. Thanks for the warm
welcome.
Second. Thanks for the quick response
and ideas by all three of you (Derek, Richard, and Bob).
Answers to your questions Derek:
Ive
been told we usually release on a quarterly cycle although that isnt
set in stone (I just started
Has anyone encountered this? I'm trying to install a single sign on isapi filter, and at the very end of the installation when it says install to metabase or something like that, the thing hangs and eventually all resources are eaten up causing the need for a reboot.
Is this what was fixed in
It turned out to be Local Security Policy issue than of password.
Adding the service user to the Log on as a service rights
under Administrative Tools - Local Security policy /Secutity
Settings/Local Policies/User Rights Management in XP and similar one
in 2003 fixed the issue.
Apparently
I'm having a lot of trouble getting an MSI installer to work with file names or folders containing characters like Á or ó. Whenever I attempt to run the .msi it says that ?_propos_du_bouton_d_ic?ne.htm was an invalid file name, but that's not what I even named the file. The file was called
I think there is already a Bug or Feature Request tracking this. Yes, it's
possible... just hasn't been done yet.
-Original Message-
From: Chandra Rentachintala [mailto:[EMAIL PROTECTED]
Sent: Friday, July 28, 2006 10:52 AM
To: Chandra Rentachintala; [EMAIL PROTECTED];
Is there a way to do what I want
to do. I would think that this can be done. Many installers do this, but
maybe they use a C++ custom action which does the registry for them. Any
thoughts?
John
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 27, 2006 3:50 AM
To:
Tallow (for WiX 2.0) and Heat (for WiX 3.0) are the standard ways of
creating WiX authoring based on existing data like directories full of files
and such.
Note that to do this the right way is somewhat non-trivial. The thing
about WI is that you shouldn't be changing component GUIDs all the
WiX 3.0 currently has the ability to read library (.wixlib)
files generated by the WiX 2.0 version of the toolset. However,
weve recently identified several reasons why wed like to stop
maintaining backwards-compatibility with the 2.0 format. The overall goal
here is to make the changes
25 matches
Mail list logo
