The ComponentGroup/@Directory will not jump a reference. Today,
everywhere I can think of, the inheritance only flows the actual element
parent/child relationships.
On Wed, May 23, 2012 at 2:35 PM, Nick Ramirez nickra...@hotmail.com wrote:
The default WiX setup project template in WiX 3.6
What version of Burn are you using? Those sound like old errors that I
think were fixed in more recent builds of Burn. The security ID issue could
be a problem if they mucked up the permissions of %ProgramData% or certain
parts of the registry.
The full line from the log file would probably help.
1. Options page is populated from an InstallFolder Variable.
2. Add the Windows Installer package as a package in your Chain.
On Wed, May 23, 2012 at 9:56 PM, Sean Farrow
sean.far...@seanfarrow.co.ukwrote:
Hi:
I'm trying to move a product I'm involved with to a burn bundle.
I using the
Thank you your solution works.
My problem is solved
--
Daniel DA COSTA
Service Informatique
53, rue La Fayette
75009 Paris
Tél : 01 78 09 82 52
Have you tried running regsvr32 on the DLL directly on an XP machine?
I've seen issues with DLLs where the developer is using a Windows 7
machine and has unknowingly used an API call that's just not available
on XP.
Kelly I saw those same errors a while back which were caused by our AV
(Symantec Endpoint Protection v12) heuristic detection blocking Burn from
extracting stuff from itself when it was unsigned. We reported it to Symantec
but other AV products may have similar issues.
Have you tried signing
http://wix.sourceforge.net/manual-wix3/heat.htm
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the Virtual Environment**
Integrated Environmental Solutions Limited. Registered in Scotland
Yes I have, when I run regsvr32 on XP I get LoadLibrary(the dll I'm using)
failed - The specified module could not be found
On Thu, May 24, 2012 at 3:18 AM, Rob Hamflett rob_hamfl...@sn.scee.netwrote:
Have you tried running regsvr32 on the DLL directly on an XP machine?
I've seen issues with
Sounds like either as Rob says an API call which doesn't exist on XP or a
missing dependency (essentially the same thing).
Open your DLL in dependency walker on XP see what it says.
Once you get it registering manually, use heat to register it the proper way in
your MSI.
Palbinder Sandher
I opened the dll with dependency walker and this is the error that I
received
Error: At least one required implicit or forwarded dependency was not found.
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a missing
There are 3 files the that give an error opening a file they are:
MSVCP100.DLL
MSVCR100.DLL
MSJAVA.DLL
On Thu, May 24, 2012 at 9:56 AM, Jelani Jackson jeljac...@gmail.com wrote:
I opened the dll with dependency walker and this is the error that I
received
Error: At least one required
Slipstreaming MSP's logs:
http://upload.iesve.com/downloads/burn_issues/shared_content_clean_install_burn.log
http://upload.iesve.com/downloads/burn_issues/shared_content_clean_install_msi.log
- this is where it sticks with the Install button that does nothing when
clicked no matter how long you
Hi All,
Please help with the WiX problem described below.
Using VS2010 ultimate, I made an installer with four features based on the WiX
Mondo UI . On installation or removal, a dialog should appear to reguest
additional information if the user selects one or both of two particular
Hello,
I have successfully added my own dialogue to what would normally be the *
WixUI_FeatureTree* user interface but I do have a problem finding out *what
*features have been selected in the *CustomizeDlg *dialogue. I do need to
call different custom actions depending on what has been selected.
It sounds like you're missing the VS 2010 redistributables on the XP
system.
Mike Schlueter
Software Engineer
Phoenix Contact USA
Ann Arbor, MI
(734)205-5410
mschlue...@phoenixcon.com
From: Jelani Jackson jeljac...@gmail.com
To: General discussion for Windows Installer XML toolset.
On 24-May-12 10:02, Pally Sandher wrote:
However Bob you're incorrect, WiXUI perfectly supports indirect uninstall
with full UI. You can run the MSI you used to install the product you'll
get that button saying Uninstall and the rest of the prompts labelled
accordingly.
That's maintenance
That makes perfect sense then. To use the Directory attribute feature, I will
just have to nest the components inside of the ComponentGroup. With so many
ways to arrange these elements, I wonder which way is the cleanest or most
readable or most maintainable.
--
View this message in context:
You can put an ampersand in front of the name of the feature to check its
action state. There's some more info about it here:
http://wix.tramontana.co.hu/tutorial/com-expression-syntax-miscellanea/expression-syntax
and here:
I've been trying to completely suppress any FilesInUse dialogs from
appearing, because I want to handle it. I've tried
setting MSIRESTARTMANAGERCONTROL=Disable, that seems to prevent restart
manager, which is good. I've also tried creating my own FilesInUse dialog
and setting Hidden=yes, that
Also it'd be much less convoluted to show your custom dialog before the
VerifyReadyDlg rather than after and make more a lot more sense to configure
the installer before the user clicks install rather than after.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0)
Thanks for your response Nick. However, I am using the SelectedFeature syntax
to access the feature action state and the !SelectedFeature syntax to access
the feature installed state. My issue is that the installer works perfectly
for complete initial install and complete removal. The
I understand your point, however, the appearance of the dialog is dependent on
which features are selected during the installation. Refer to my response to
Nick's comments for a better expalnation of what I am trying to do. Thanks.
Regards,Chris.
From: pally.sand...@iesve.com
To:
Those top two are Visual C++ 2010 C runtime support Dlls, typically supplied
with this type of thing:
http://www.microsoft.com/en-us/download/details.aspx?id=
or with merge modules that came with Visual Studio 2010. You'll probably need
a minimum of XP SP3 (see the link, system
I'd recommend using the latest weekly build over RC0 -
http://wixtoolset.org/releases
If you're still getting those issues after updating I would try it with AV
disabled to make sure it's not getting in the way.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0)
Hi:
Is there any way that InstallFolder could be populated from an msi?
Cheers
Sean.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 24 May 2012 07:27
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Specifying a default
I've never got it to work for me to show attachments. Maybe you could paste
the relevant code in? So, when it doesn't show the custom dialogue in
maintenance mode, do you mean that it skips it and goes to the dialogue
after that?
--
View this message in context:
Has anyone tried with success to allow dynamic metadata to be included
in a custom managed bootstrapper application? I see how the BalExtension
is doing it via CustomTable and Row elements. I was hoping for a means
to inject arbitrary data into the application data per project using the
same MBA.
That decision we did not make for you. smile/
On Thu, May 24, 2012 at 8:03 AM, Nick Ramirez nickra...@hotmail.com wrote:
That makes perfect sense then. To use the Directory attribute feature, I
will
just have to nest the components inside of the ComponentGroup. With so many
ways to arrange
I could interpret that question a few different ways. Can you be more
specific about what you want?
On Thu, May 24, 2012 at 11:38 AM, Sean Farrow
sean.far...@seanfarrow.co.ukwrote:
Hi:
Is there any way that InstallFolder could be populated from an msi?
Cheers
Sean.
-Original
Hi:
Ok, I have a bundle that is going to install either a 32-bit or 64-bit msi
after installing the windows installer prereq. What I'd ideally like is the
InstallFolder variable to pick up the install directory from the msi so going
down from either program files/program files64--perhaps use
30 matches
Mail list logo
