Mark Line wrote:
What would be the best way to edit the config file? is it possible to edit
the file before install or should it be done after the installation? [The
config file is not XML, its plan text]
The only two standard file modification actions are XML files (via WiX's
XmlConfig an
Thomas Svare wrote:
> There's a way to do it through group policy but I can't remember how off
> the top of my head. Do a search on voicewarmup and you'll find the
> registry entries you can set before the installation.
>
Copy this to a .reg file and keep it handy for new machines and
unsuspe
Alex Steen wrote:
> Yes, there are other files, files that have nothing to do with the
> installer(I've tried installing to a folder with other things already
> present or adding files post install, but both way end up with the same
> result) that are getting deleted when I run an uninstall. Any f
Brian Poploskie wrote:
I'm using some file keys in custom actions, for example [#MyFile].
This was working fine until I broke the core wxs file up into multiple
files containing fragments for easier maintenance. Since I've done
this the file references don't seem to be evaluating to anythin
Jimbo,
I see your predicament!
Again, InstallShield has the ability to add files via wildcards etc (not
that I'm promoting InstallShield, for the cost its pretty clunky), can't
remember the exact term.
A question I would ask is that if you have 16,000+ files that are being
changed, added, del
Thanks Dave,
I understand what your saying, but I'm managing installers
with 16,000+ files. That's not something I'm going to do manually and
files can be added and deleted on a daily basis. Heat looks good from my
prospective however its missing a critical piece, and that's (what
b
Jimbo,
In addition to what Mike was saying (regarding understanding what's been
generated), the WiX source files should be created during the development
phase of a project (early). The wxs files will be developed as the project
is developed, I would consider it one of the most important parts of
The reason for the warnings is that the VS CRT merge modules aren't
particularly well authored. A validation run on the merge modules would have
revealed these problems to the authors at Microsoft.
Windows Installer databases are really property databases - not using a
fixed schema, just a bunch o
Hey mike,
What would you consider the future of heat? I don't see heat
as a starting point at all, I see it as a beginning of an automated
build extractor/creator. I know its not there yet, but its really not
that far off. I need create installers (out of TFS) daily in a
repeatable
Generally you should consider Heat's output as a starting point, not a final
product. You need to understand what's been generated.
Heat captures the raw registry output from running the DllRegisterServer
output; it then transforms what's been harvested into the higher-level
values. Anything le
Vince,
There's a way to do it through group policy but I can't remember how off
the top of my head. Do a search on voicewarmup and you'll find the
registry entries you can set before the installation.
Thanks,
Tom
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Be
Thanks Tom. How do I produce a log file from the Active Directory install?
Since I can't specify arguments for the MSI execution (e.g. /l*vx log.txt).
Cheers,
Vince
Thomas Svare wrote:
>
> Vince,
>
> A diff between verbose logs for a user initiated install and the active
> directory install
Hello
In the help of WiX 3.0.3029.0 I saw the following for "Quiet Execution
CustomAction"
If you want to run more than one command line in the immediate sequence
then you'll need schedule QtExec multiple times and set the
QtExecCmdLine property (using a type 51 custom action) right before you
wan
Vince,
A diff between verbose logs for a user initiated install and the active
directory install would probably point out the issue. With the active
directory install you don't have UI and I believe the entire install
runs as local system.
Thanks,
Tom
-Original Message-
From: [EMAIL PRO
Hi,
I'm trying to deploy my installer package through Group Policy from Windows
Server 2003 to Windows XP clients. The software is being distributed through
"Computer Configuration" and "assigned" to the clients computers (as opposed
to "published").
The setup installed all the files, system reg
It's not that I want to know where it was previously installed.
It's that I want to know if a configuration file already exists in the
path the user selects (INSTALLDIR). If the configuration file already
exists, I don't want to give the appearance that it can be changed; i.e.
I am presuming th
You could write a permanent registry entry containing the path that the
user selected, then read the registry entry when the install is run
again to find out where it was installed before.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ar
extern "C" UINT __stdcall DropDatabase(MSIHANDLE hInstall)
{
…
hr = WcaInitialize(hInstall, "DropDatabase");
ExitOnFailure(hr, "failed to initialize");
hr = ::CoInitialize(NULL);
ExitOnFailure(hr, "failed to intializ
I've been trying to figure out how to install a CA certificate for a
while now without a whole lot of luck. I found the IIS extension
listing for the certificate element, and I've run into a couple of
different errors with it. I've tried inserting this markup:
If I put this in its own el
Hi,
I didn't get a response to this yet. Can someone pls help me here?
Thanks.
From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: RE: Database is trying to be
dropped when it was not created during current installDate: Sat, 28 Jul 2007
18:23:19 -0700
Hi,
I am creating a database using the followi
I had seen one product that used DemoShield and I knew that DemoShield was
no longer available. But I hadn't found that Installsite link you gave.
Thanks Friedrich!
Jim
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Friedrich
Brunzema
Sent: Saturday, July 28, 2007 5:45 AM
Werner, Harvey D wrote:
> I need to update the PATH environment variable to prepend the value of
> "[TARGETDIR]\bin" during our product installation.
>
You need
Action='set'
below, and I believe you have to do a CA to get/manipulate the value to set.
Am I the only one who absolutely hates it
I think you're just missing [EMAIL PROTECTED]"set".
Rob
Werner, Harvey D wrote:
> I need to update the PATH environment variable to prepend the value of
> "[TARGETDIR]\bin" during our product installation.
>
> How is this done in WiX? I tried using the Environment element, but it
> does not chan
I need to update the PATH environment variable to prepend the value of
"[TARGETDIR]\bin" during our product installation.
How is this done in WiX? I tried using the Environment element, but it
does not change PATH at all.
Obviously, I do not want to delete PATH during uninstall,
Hey everyone,
I'm currently attempting to write an installer using wix 2.
I have all the files and set up dialogs working correctly. I have an extra
dialog which is added to the mondo wixUI by changing the property on the
next buttons
OmniCfgDlg is a simple dialog which allows the user to i
Yeah, I agree that heat will produce a lot of RegistryValue
elements that are not related to the DLL being looked at (like you said,
usually VB Runtime related). Which is fine since heat shouldn't be used
for automated builds etc, and the output should be hand-tooled/cleaned
up. But I wo
Yes, there are other files, files that have nothing to do with the
installer(I've tried installing to a folder with other things already
present or adding files post install, but both way end up with the same
result) that are getting deleted when I run an uninstall. Any file that
is within the fol
We are trying to mitigate an admittedly pathological case during
installation.
1. User installs application to other than default directory. The
installation installs a permanent, never-overwrite configuration file
which (among other things) specifies a file store [1] path which is
specified by
Thanks John.
Yeah, I agree that heat will produce a lot of RegistryValue elements that
are not related to the DLL being looked at (like you said, usually VB
Runtime related). Which is fine since heat shouldn't be used for automated
builds etc, and the output should be hand-tooled/cleaned up. But
> From reading blogs on the web, the way to add the merge modules for
> the VC8 CRT libraries is shown in the WXS code below. But I get a lot
> of warnings in the process.
>
> We are using Visual Studio 2005 SP1 and Wix v3.0.2925
>
> What is the reason for all the warnings?
>
> What can be done
I've been using WiX 3.0.2925 to install some of our COM DLLs
(created by Visual Basic 6.0 SP6).
With WiX 3.0.2925 when I use:
"heat file MyLibrary.dll -out MyLibrary.wxs"
I will often get a mixture of entries (which is what I
want)
I'm using 2.0. It's hard enough convincing people around here to use
new tech, let alone pre-release tech.
They are deferred but all scheduled before InstallFinalize. They're all
on the same schedule as they were before I moved everything to fragments
and they worked fine before.
Brian Po
I'm using some file keys in custom actions, for example
[#MyFile]. This was working fine until I broke the core wxs file up
into multiple files containing fragments for easier maintenance. Since
I've done this the file references don't seem to be evaluating to
anything. I get empty st
> I'd like to get my bootstrapper exe to be built while I'm
> building my Wix file instead of going into the command line
> and doing it separately. I figured I could do some kind of
> ExeCommand to get it to work but I'm not quite sure where or
> how to add that in. Can Wix do that? I know
I'm using some file keys in custom actions, for example [#MyFile]. This
was working fine until I broke the core wxs file up into multiple files
containing fragments for easier maintenance. Since I've done this the
file references don't seem to be evaluating to anything. I get empty
strings in th
Hello,
>From reading blogs on the web, the way to add the merge modules for the VC8
CRT libraries is shown in the WXS code below. But I get a lot of warnings in
the process.
We are using Visual Studio 2005 SP1 and Wix v3.0.2925
What is the reason for all the warnings?
What can be done to fix
36 matches
Mail list logo
