No, I just assumed it would work. On to the docs, and thanks for
pointing me straight!
Barry
On Sun, Jul 29, 2012 at 2:29 PM, Rob Mensching r...@robmensching.com wrote:
Did you follow the instructions for signing a bundle in the WiX.chm? It's
not as simple as signing the final executable
Interestingly, if I don't codesign the bootstrapper (individual MSIs are *
not* signed), the installer succeeds.
On Fri, Jul 27, 2012 at 10:25 AM, Barry Wark ba...@physionconsulting.comwrote:
I've built a boostrapper installer with Burn v3.6.3109. The installer
fails with the following log. I
)? Any suggestions?
[046C:0F9C][2012-07-27T10:22:50]: Burn v3.6.3109.0, Windows v6.1 (Build
7600: Service Pack 0), path: C:\Users\Barry Wark\Downloads\OvationInstaller
(2).exe, cmdline: ''
[046C:0F9C][2012-07-27T10:22:50]: Setting string variable 'WixBundleLog' to
value
'C:\Users\BARRYW~1\AppData
:\Program
Files\MATLAB)?
Thank you,
Barry
--
Magic Quadrant for Content-Aware Data Loss Prevention
Research study explores the data loss prevention market. Includes in-depth
analysis on the changes within the DLP market
, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: Barry Dorrans [mailto:bdorr...@microsoft.com]
Sent: 28 July 2010 02:15
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Adding a feature specific EULA
Last one. I hope
**Design, Simulate + Innovate with the Virtual Environment**
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: Barry Dorrans [mailto:bdorr
Message-
From: Barry Dorrans [mailto:bdorr...@microsoft.com]
Sent: Tuesday, July 27, 2010 07:34
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Adding a feature specific EULA
Ah that makes sense, insert the second EULA after the feature tree if the
feature
Oops never mind I see where my fat fingers went astray :)
-Original Message-
From: Barry Dorrans [mailto:bdorr...@microsoft.com]
Sent: Tuesday, July 27, 2010 13:41
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Adding a feature specific EULA
So I'm
Arrghh.
So almost there, well, maybe. Light is throwing (but not appearing in the VS
Error List Window - I see them in output)
error LGHT0204: ICE03: Not a valid foreign key; Table: ControlEvent, Column:
Control_, Key(s):
.'
Subject: Re: [WiX-users] Adding a feature specific EULA
Does the dialog named SupplementalEulaDlg have a Control Id=Next ...
inside of it?
-Original Message-
From: Barry Dorrans [mailto:bdorr...@microsoft.com]
Sent: Tuesday, July 27, 2010 3:56 PM
To: General discussion for Windows
Last one. I hope.
I have my dialog working as expected now, and it appears in the dialog flow. I
now, finally, want to only make it appear if neither of two particular features
have never been installed, and either is being installed.
I thought I'd try to get one condition working first and
like to ensure they accept it there and then, if they
don't then the feature doesn't get selected. At some point the same EULA will
control access to two features.
Is this possible? Where should I start looking for instructions?
Thanks in advance,
Barry
I've seen a post or two about a situation wherein the environment Path
is modified to include a new directory reference which is to be used
later during the same installation session. Specifically, I have used
the Environment element to append a directory reference to the Path
variable then,
Bob Arnson-6 wrote:
barry wrote:
Tried that other forum but they said to try WIX newsgroups!
If your WiX-built MSI works, then it's not WiX and it's not Windows
Installer. Sorry, I know it's not much help, but what you're describing
doesn't make sense unless the bootstrapper
Bob Arnson-6 wrote:
barry wrote:
Do you know where is the best place to post my problem for the
bootstrapper
experts?
Try
http://social.msdn.microsoft.com/Search/en-US/?Refinement=112query=BOOTSTRAPPERrq=rn=.
--
sig://boB
http://joyofsetup.com
barry wrote:
Hi There,
After another long day trying to isolate this problem I think I am making
some progress..
I changed the Addin GUID to a new guid and regenerated the wix fragment
and reinstalled on my development box. The Addin installs correctly and
gets loaded in word
Wilson, Phil wrote:
A couple of things:
1, It looks like your versions are 1.0.* and the compiler will generate a
new one every time you build. If you heat once and then rebuild your
add-in you're going to have a mismatch. I recommend setting a complete
version. If you haven't
, PublicKeyToken=b77a5c561934e089.HTM
http://www.padraiglarkin.com/temp/WhereRefBind!Host=(LocalMachine)!FileName=(DTIOfficeAddIn.dll).HTM
WhereRefBind!Host=(LocalMachine)!FileName=(DTIOfficeAddIn.dll).HTM
Any help much appreciated
-Barry
--
View this message in context:
http://n2.nabble.com
barry wrote:
Hi there,
I am having some problems registering my com assembly. This assembly is a
dot net office addin dll.
I used the following command to generate the registry keys:
heat file DTIOfficeAddIn.dll -out MyComExposedLibrary.wxs -scom
This generated the registry keys
Bob Arnson-6 wrote:
barry wrote:
anyone know how adding a bootstrapper could cause comboboxes to freeze on
a
custom ui dialog?
You probably want to talk to the bootstrapper folks.
--
sig://boB
http://joyofsetup.com/
Thanks Bob,
Do you know where is the best place to post
bump,
anyone know how adding a bootstrapper could cause comboboxes to freeze on a
custom ui dialog?
cheers,
barry
barry wrote:
Hi,
I am having a strange problem with my installer.
Basically i have an installer for a c# com office addin. It uses a custom
UI that has a combo box
hi, anyone got any ideas
or if anyone could see if theres anything wrong with the way im setting up the
comboboxes that would also be a great help!
or if anyone can tell me the correct way to create a bootstrapper in case my
approach is causing the issue
cheers,
barry
--
View
of RegistryValue elements out flat. Both ways work.
-Original Message-
From: Barry Larkin [mailto:barrylar...@gmail.com]
Sent: Tuesday, January 20, 2009 03:33
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] installing Outlook Primary Interop Assemblies
hi guys
hi guys,
thanks for that, we will look into the setupbld options for bootstrapping
yes the protocol handler is just registry keys, i couldnt find a clean
example of creating registry keys within registry keys int the tutorial.
cheers,
barry
Re: [WiX-users] installing Outlook Primary Interop
to define a custom protocol handler in the registry:
http://msdn.microsoft.com/en-us/library/aa767914(VS.85).aspx
if anyone could show me how to create these registry enties using wix i
would be very grateful!
Kind regards,
Barry
Hello,
I just started using WiX about a week ago, but I have been reading non
stop all week. I want to have a dialog (A) prompt the user for an
install path. Next I want the installer to check if a certain file
exists at the location the user chose for the install. If the file
exists I would
26 matches
Mail list logo