Not with the default templates, you would need to customise them to add some
text.
Neil
-Original Message-
From: Alain Forget [mailto:afor...@cmu.edu]
Sent: 26 August 2013 23:56
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Add text to final window in burn bootstrapper/insta
Cool, thanks Phil. I was hoping for some native support for DCOM in WIX
utilities or something like that... but alas I don't think it exists.
I hadn't discovered this SDK sample before though, so it is very helpful.
I would just build this into a custom action for the WIX installer
obviously?
C
Thanks for both replies. I am indeed on a x64 machine and have no idea how to
distinguish between x86/x64 registries. I've probably created the key in the
wrong one. Any pointers? To open the editor, I type in "regedit"
If not that, then how should I make this conditional:
> >
> >
>
Hi all,
Our installer bundled with burn currently posts a simple "Setup Complete"
message when the install is done. How can we add additional text on this last
window when the install is complete?
Thanks,
Alain
--
Int
I don't know if there's anything more recent, but DCOMPerm can be used for
this:
http://msdn.microsoft.com/en-us/library/aa242178(v=vs.60).aspx
Phil Wilson
On Sat, Aug 24, 2013 at 4:20 AM, Benjamin Sole wrote:
> Hi there, does anyone know if there is a way to change the launch and
> access per
This is what I don't understand. You said the ini file is packaged in the
MSI file, therefore you know what this model thing is (in the ini file)
when you build the MSI file. Why bother to try to find it at install time?
Even it's awkward in your build for some reason, a post build step could
extr
I finally got a chance to look, and it appears that your dialog sequencing is a
little inconsistent and pressing "Next->Next->Next" when applying a patch
appears to be changing your installation type (check your verbose log for the
sequence of property changes).
Some properties your UI uses are
What often happens is that there is a custom action to set the default
INSTALLDIR location to the program files folder, and people forget to make
it conditional, with a condition like NOT INSTALDIR. You may find that if
you set INSTALLDIR on an msiexec command line it would also get
overwritten. T
You read it during InstallFiles? How?
> Date: Mon, 26 Aug 2013 16:37:12 +0530
> From: dileep.sanamp...@gmail.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] [Wix]: Copy INI file to WINDOWS folder before
> 'InstallFiles' action.
>
> Hi Blair,
>
> I should copy the INI file i
Looking at the path depth on your assembly, you could have hit some sort of
.NET find next limitation. The path is also rather long at 155 characters
although still within the 260 character .NET limit. I prefer my builds to have
a considerably flatter directory structure than this for maximum
0xc0fd is "Unknown Software Exception." It's usually related to a stack
overflow somewhere.
--
John Merryweather Cooper
Build & Install Engineer -- ESA
Jack Henry & Associates, Inc.(r)
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-O
Hi all:
Wondering if anyone can shed light on this - have a huge application where
patch creation was working fine till Friday last week. After investigating,
*NO* configuration changes to my build system were made other than some updates
from Microsoft. The system consistently stops on the
Hi Blair,
I should copy the INI file in C:\Windows folder before 'InstallFiles'
action.
I have to read that INI file information and needs to be set Property
values for Modelname.
Thanks...
On Mon, Aug 26, 2013 at 4:08 PM, Blair Murri wrote:
> It would be much easier to copy it to C:\Windows
"Adding" is not overridding, it is creating.
That would suggest that there is no InstallDir value at
HKLM\Software\Acme\Foobar 1.0
Do you have a 32-bit MSI and are trying to read a 64-bit registry location, per
chance? Or vice versa?
> From: rob...@softdev.net
> To: wix-users@lists.sourceforge.n
It would be much easier to copy it to C:\Windows folder either as part of
InstallFiles or right after InstallFiles action. Copying it there before
InstallFiles is a fair bit of work.
What are you trying to do? Maybe we can help you with that.
> Date: Mon, 26 Aug 2013 12:54:05 +0530
> From: dilee
Hi All,
How to copy INI file in C:\Windows folder using Wix created MSI file?
INI file is packaged in MSI.
Before InstallFiles action in MSI, This INI file should copy in C:\Windows
folder.
Please help me to solve this.
---
16 matches
Mail list logo
