> You need a
> separate 64-bit installer for this.
Yes, of course, that's what I have (well, actually, I've got 1 script
for both x86 and x64 plus a bit of trickery to get it all to work).
Anyway, got it working. I was accidentally including the x86 binary
instead of the x64 one in my installa
Okay I've spent a lot of time trying to figure out my following wix problem
but I've yet to find an solution that works.
The original goal was to run a bat file that had already been written right
at the welcome screen that would do a hardware requirements pre-check at the
beginning of the i
Hi,
I has two product MSI setups, A.msi and B.msi. I add two new shared files
installed to "Program Files\Common Files" through a merge module for both
Product A service pack 1 and Product B service pack 1. I created A_sp1.msp and
B_sp1.msp.
I have A and B installed on one machine. I also app
Choosing the drive with the largest available space is a function of the
Windows Installer, not Wix.
You can set the ROOTDRIVE property if you are certain where you
application should go.
http://msdn.microsoft.com/en-us/library/aa371372(v=VS.85).aspx
-Original Message-
From: Prabhat_IE [
Not to discourage you but in early 3.0 versions I have encountered bugs that
prevented me from creating binary delta patches with Pyro. Patching the full
file was fine. I was too busy to follow up on the bugs or check if they were
fixed in later releases so I don't know what is the state right n
BTW, one last comment. I'm often irritated by some of the crap packages that
I have to bootstrap and we often get blamed when things go wrong that were
outside of our control. Because of this we created a novel use case: The
bootstrapper that only does prereqs and not our MSI. In other
Agree with all you said except it's not paying for the bootstrapper
functionality that irritates me, it's that they have it too tightly couple with
InstallShield. I'd love to have a project type that allowed me to take an
externally generated MSI ( say in WiX ) and then wrap it with InstallS
That is the correct solution. Heat.exe exports COM from .NET assemblies
without issue for anything I've given it including DLL/TLB pairs.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate
On Wed, 1 Sep 2010 08:34:37 +0100
Bruce Cran wrote:
> I'm having problems installing a multi-file mixed-mode .NET 4.0
> assembly to the GAC using WiX 3.5.2030.
So it appears that it's trying to install the assembly to
c:\windows\assembly instead of c:\windows\microsoft.net\assembly based
on the
Hi,
I'm using Wix 3.5.2020 and the WixIIsExtension and WixUtilExtension
Regards
Valentijn
--
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2
Hi,
I'm having problems installing a multi-file mixed-mode .NET 4.0 assembly
to the GAC using WiX 3.5.2030.
I have a mixed-mode C++/CLI assembly built using Visual Studio 2010 that
depends on a native DLL so I've built it with /assemblylinkresource to
create a multi-file assembly with the nativ
After upgrading wix the output path of one of my wix projects has changed
The locale directory is gone
Output used to be : Debug\nl-nl\
But is now Debug\
More details
Wix build 3.5.2020
It happened for multiple solutions that have more then one setup
Wix projects are located in a Solution folder
As far as I'm aware 32-bit shell extensions don't integrate with 64-bit
Explorer. You need a
separate 64-bit installer for this.
Rob
On 01/09/2010 05:59, Michel wrote:
>This has probably been asked before (but I can't find a good way to
> search this list?):
>
> I've created my wix install
13 matches
Mail list logo
