Glad you got this worked out. In my case, the problem was that I wasn't
specifying ALLUSERS=1, so I was inadvertently doing a per-user install
instead of a per-machine install. When the Windows service (running as
LocalSystem) tried to instantiate one of the COM objects, it couldn't
find the regist
Richard wrote:
> RegMon will reveal all. You can get it from the sysinternals portion
> of Microsoft's web site.
Not always. As I said from my original post, I monitored the
installation using ProcMon (the successor to RegMon), and it looked like
everything was okay. The problem turned out to be
I know this isn't the exact forum for this, but I'm really confused and
don't know where else to turn. I'm in the process of moving our
installer to an msi-based install using WiX. Our application is fairly
complex, including .NET assemblies, a client-side application, Windows
services that run on
tor though..
/Simon
On Tue, Aug 12, 2008 at 5:35 PM, Evans, Jim <[EMAIL PROTECTED]>wrote:
> I'm having a problem writing a value to an XML file using XmlConfig (WiX
> 3.0.4401). Here is a model XML file with the structure I have:
>
>
>
>
>
>
&g
The workaround mentioned in the bug you supplied the link to works around my
problem nicely. Thanks for the heads-up.
From: Meyer, Shawn [mailto:[EMAIL PROTECTED]
Sent: Tue 8/12/2008 12:21 PM
To: wix-users@lists.sourceforge.net
Cc: Evans, Jim
Subject: RE: WiX
I'm having a problem writing a value to an XML file using XmlConfig (WiX
3.0.4401). Here is a model XML file with the structure I have:
...
I need to set the server attribute of the Default element. Here is my WiX code
for XmlConfig:
When I try to
I'm pretty sure this has been asked on the list before, but searching
didn't yield a definitive answer for me. In my current project, I'm
working on migrating our current installer to using MSI via WiX, and I
thought I'd try WiX v3. In the project, I have several COM components
that were written us
What are some of the "best practices" for authoring the installation of
COM components? Obviously, I know selfreg is evil. When it comes to the
registration of COM components, should you author the registry entries
within the same Windows Installer component, or as separate components?
I've argued
have much luck
there.
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
--- On Thu, 7/3/08, Evans, Jim <[EMAIL PROTECTED]> wrote:
> From: Evans, Jim <[EMAIL PROTECTED]>
If I have a text file (or other unversioned resource) that I want to
overwrite during a minor update, is it ok to give the file a "version"
using the DefaultVersion attribute of the File element? It seems like
this works and forces the overwrite only if I increment the
pseudo-version. I just want t
Rob Mensching wrote:
>> Am I going to have to resort to a custom action to read the settings
and
>> propagate them? If so, ugh. It seems like there should be a WiX
custom
>> action for simply reading the contents of an XML file (value or
>> attribute) and putting the value into a property.
>
> Open
Thanks for this, Chris. I hadn't considered the implications of XML
schema changes in my config file. Since I'm distributing so-called
"small updates" as reinstalls using an updated .msi, it's likely that
the create date of the config file will be different (since I'll have
rebuilt the project), an
My installer is working quite nicely now for the initial installation.
In thinking about my upgrade strategy, I've decided to distribute
so-called "small updates" as reinstalls of an updated .msi. However, I
have two components (my app config file and the component that writes
user settings to the
I have a question about the XmlConfig custom action. My application is a
.NET application, and is deployed with an application.exe.config file.
Based on properties gathered during the installation, I want to update
the values in the config file. Here's the relevant portion of my config
file.
n 20, 2008 at 3:25 PM, Evans, Jim
<[EMAIL PROTECTED]> wrote:
> Thanks Jason, this gets me most of the way to where I need. Let me see
> if I understand this correctly:
>
> * I create two elements in my WiX project, one for the
> immediate custom action, one for the defer
this helps.
-Jason-
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Evans, Jim
Sent: Friday, June 20, 2008 4:24 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] DTF custom action questions
My installation creates and then interac
My installation creates and then interacts with a SQL Server database.
Up until now, I've been able to do everything I need to do from WiX
using the standard extensions, but now I'm facing a problem for which I
need a custom action.
I have to import some data into my database, but I need to mod
s Installer XML toolset.
Subject: Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3
roadmap.
If you write it, I'll add my name. I'd even be happy to try to find the
right people to send it to.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
end a letter to
the team to ask them to implement a solution like the .NET Framework.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Evans, Jim
Sent: Friday, June 06, 2008 10:02
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-
Bob Arnson wrote:
> It's unlikely to change the date when the bootstrapper becomes
> available. Working on it in the v4 branch gives us the flexibility to
> ship it in stages and not be "forced" to do a more limited release
just
> to ship v3. Also note that there's nothing that ties the bootstra
This is sorely disappointing to me personally. Quite frankly, I need the
bootstrapper. I hate that I'll be waiting for WiX v4 to get it. In an
earlier email, Rob, you mentioned that your team had the design pretty
well nailed down, though the code has a long way to go. Is there any
chance that the
For what it's worth, I can only echo the comments of those who support
the idea of including the bootstrapper framework before declaring WiX v3
"released". I'm very much a novice at installation development, though
wix-users has been an incredible resource for me to ramp up my personal
knowledge ba
ovember 12, 2007 9:25 PM
To: Evans, Jim; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Monitoring progress of chained installs
Your requirements are similar to ours. We need to ask the user what
features they want to install then, depending on their answers, they may
need MSMQ and
I have a moderately complex application that I am trying to write an
installer for. The current installer does not use Windows Installer at
all, but I believe moving to Windows Installer would provide several
benefits for our customer base. Our product requires services to be
started, file shares t
24 matches
Mail list logo
