Thanks Palbinder for your reply. Well, whatever replies I've got for this issue
are convincing me for two separate MSIs for 32-bit and 64-bit Platforms resp.
I've one more query related this. I'm not sure whether to ask but still is it
possible to write inline code in WIX? If so, I could probabl
Deployment Tools Foundation (DTF) which ships with WiX provides APIs for
working with MSIs (among other things) and querying machine state.
From: Kyle Huey [ksh...@ufl.edu]
Sent: Wednesday, January 13, 2010 7:17 PM
To: General discussion for Windows Instal
The link points to ICE testing. I assume the author is looking for some
testing method that includes the actual installation/repair/remove actions.
I currently use a couple of VMs to test created MSI. To check if the
components get installed correctly I normally have a test program. E.g. if
you wa
Don't think so. Good feature request.
On Wed, Jan 13, 2010 at 11:57 AM, Chad Petersen wrote:
> Our 32-bit .NET 2.0 Web app was having difficulties on this 64-bit
> platform. Our assemblies were compiled as x86 (rather than "Any CPU")
> and they just would not load on this platform initially. If
1. Yes.
2. I'm fuzzy on old v2.0 syntax but Package/Platforms is important to set to
x64.
3. No. A 32-bit MSI can install on 64-bit OS but it will be redirected to
the 32-bit locations. If you want to install a 64-bit application to the
64-bit locations then you need a 64-bit MSI.
On Wed, Jan 13,
> From: Pally Sandher [mailto:pally.sand...@iesve.com]
> Sent: Wednesday, January 13, 2010 10:49 AM
>
> ...
> An MSI has a platform attribute which must be set to "Intel" for x86
> packages or "Intel64" for x64 packages (can also use "AMD64" for x64
> packages but it's deprecated by "Intel64").
>
>
> Hi,
>
> I have project developed using both .net 2.0 and C++ code.
> I have compiled .net code to target 64bit bit machine. i am using wix 2.0
> to create my msi package.
> i want to deploy the application in 64 bit windows 2003 server.
>
> i have below questions
>
> 1) Does wix 2.0 supports 6
http://msdn.microsoft.com/en-us/library/aa369554%28VS.85%29.aspx
On Wed, Jan 13, 2010 at 12:05 PM, Andrew Faust wrote:
> Is there an existing framework for creating automated tests for installers
> built with WiX?
>
> Thanks,
>
> Andrew Faust
>
> -
On 1/13/2010 1:28 PM, Inbar, Ron wrote:
> Is there a built-in way in WiX to create such entities or is it necessary to
> write a custom action that calls the Windows API?
>
It's not natively supported by Windows Installer nor by WiX's standard
custom actions.
--
sig://boB
http://joyofsetup
On 1/12/2010 9:11 AM, Mihail Roman wrote:
> msiexec /i Package.msi REINSTALL=ALL REINSTALLMODE=vomus
>
What's the behavior if you use the /f switch instead?
--
sig://boB
http://joyofsetup.com/
--
Throughout its 18-
On 1/12/2010 10:15 AM, Sebastian Brand (Instyler Software) wrote:
> Thanks for the clarification, I thought the shortname was always used. So in
> real life it's probably "WINDOW~1.5" on most machines ( try DIR /X ) But you
> can't be sure... Short file name generation might even be disabled.
>
On 1/13/2010 3:04 PM, Ken Halprin wrote:
> Can I use setupbld to include both msi and exe files as prerequisites before
> my wix-built msi installer runs?
>
Setupbld doesn't support running .exes.
--
sig://boB
http://joyofsetup.com/
-
On 1/13/2010 1:45 PM, pmdarrow wrote:
> I guess that's one way. It just seems a little unintuitive to show pop-up
> dialogs for the requirements. I thought about this for a little while and
> came up with another method. Create one dialog with all of the possible
> requirements if every feature was
On 1/13/2010 2:14 PM, Cody Gibson wrote:
> I've found HEAT doesn't generate any output even for a brand new empty VS2010
> C# class library project.
Might be a missing feature: Heat has to take special steps to support
different versions of the CLR so it might not have been updated for CLR
v4 y
On 1/13/2010 8:07 PM, Navid Azimi-Garakani wrote:
> Is there a particular reason why Heat.exe is targeted and compiled
> specifically against the x86 architecture?
Because an MSIL .exe runs as a 64-bit process on an x64 system, so it
couldn't load x86 DLLs. I suspect there's a need for Heat64.
On 1/13/2010 4:35 PM, Neil Sleightholm wrote:
> I think there is a bug in the output generated when a .Net COM assembly
> is processed with heat but thought I would run it past the community
> before raising it.
If the assembly writes it, Heat includes it. Sounds like a reasonable
thing to drop f
Is there a particular reason why Heat.exe is targeted and compiled specifically
against the x86 architecture? I have seen a couple of questions about this
around on the Internet but no firm answer or resolution. I briefly looked over
the Heat code (v3.0.5419.0) and there does not seem to be anyt
When I build my WIX project, it succeeds under user account A when I log in
as that person and build it myself from my Windows desktop. But when that
same user account is used from a Windows Service (think automated build
machine) the same build fails with the below errors.
I've checked the jscr
I set a bunch of different Properties depending on what is not-installed
and then display one dialog that lists all missing pre-reqs. I don't
care to show them the ones that are already installed, just those that
aren't.
I think there is a bug in the output generated when a .Net COM assembly
is processed with heat but thought I would run it past the community
before raising it. Part of the generated output includes this:
I don't think this should be include because it should already be
present on the system and
Thats the version we are installing.
Can you please point to how to get this merge module, and for future
references and for the other assemblies I need, where do you get
official merge modules for Microsoft components?
Daniel
Neil Sleightholm wrote:
> What versions are the two files? This is
Can I use setupbld to include both msi and exe files as prerequisites before
my wix-built msi installer runs?
Thanks.
--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon
Our 32-bit .NET 2.0 Web app was having difficulties on this 64-bit
platform. Our assemblies were compiled as x86 (rather than "Any CPU")
and they just would not load on this platform initially. If we set the
Application Pool advanced setting "Enable 32-Bit Applications" from
False to True that fixe
I see two directories listed below. You should only have one.
"C:\Program Files\Windows Installer XML v3\bin\heat.exe" dir
"..\..\~tmp\j2build3v_win\apps" -gg -sfrag -scom -sreg
"$(ProjectDir)..\..\..\~tmp\j2build3v_win\apps\eu" -out
"$(ProjectDir)gen_fragment.wxs" -template:fragment
Should be:
This doesn't sound like a WiX or MSI issue. You should create a log file
using the '/lvx* c:\out.log' and read the log to make sure the correct
username and password are being set.
Also, make sure the user name has the domain before it (e.g.
"mydomain\myusername")
Brian Rogers
"Intelligence remov
Basically you make them elevated by marking them deferred and sequencing them
between InstallInitialize and InstallFinalize.
Phil Wilson
-Original Message-
From: Andy2k8 [mailto:appr...@gmail.com]
Sent: Wednesday, January 13, 2010 10:25 AM
To: wix-users@lists.sourceforge.net
Subject:
I've found HEAT doesn't generate any output even for a brand new empty VS2010
C# class library project. Here is what the output window contains when I try to
build a simple installer containing only the brand new empty VS2010 C# class
library project:
-- Build started: Project: ArtOfTest.De
I guess that's one way. It just seems a little unintuitive to show pop-up
dialogs for the requirements. I thought about this for a little while and
came up with another method. Create one dialog with all of the possible
requirements if every feature was selected and selectively gray-out the ones
t
Hi,
Is there a built-in way in WiX to create such entities or is it necessary to
write a custom action that calls the Windows API?
Thanks,
Ron
The information contained in this message may be confidential and legally
protected under applicable law. The message
I have the following immediate custom actions sequenced during upgrade
ExportRegistry - to export a specific hive on windows registry as .reg file
ModifyRegistry - to make a few modifications for the new product
ImportRegistry - to import the .reg file
and the CAs are scheduled as
ExportRegist
I am in the midst of upgrading our product to be VS 2010 compatible. We're
using WIX to generate a .msi installer. I've upgraded to WIX 3.5.1309.0 and
have run into a snag.
Specifically I'm having a problem with the HEAT tool in this version. It is
having trouble working with our VS2010 convert
Is there an existing framework for creating automated tests for installers
built with WiX?
Thanks,
Andrew Faust
--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-cla
You will need two searches: one for the 32-bit and one for the 64-bit
search.
-Original Message-
From: Vishwajit Walke [mailto:vishwajit.wa...@matrikon.com]
Sent: Wednesday, January 13, 2010 12:51 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to handle Registry Redirecti
Those warnings are known and expected. The error is the reason for the build
failure, but that error seems to be missing text in this version of the
email (and I couldn't find the original email from Igor that Ricky is
responding to).
If the misaligned foreign keys can be identified, we can help w
Hi,
I have some problems to migrate from WIX 3.0.4707 to WIX 3.0.5419 because the
arguments of HEAT.EXE changed.
usage: heat.exe harvestType harvestSource -o[ut]
sourceFile.wxs
What is meant with the new argument harvestSource?
The old command looks like this:
"C:\Program Files\Windows Installe
Use Win64="yes" in your RegistrySearch Elements to force them to check
the normal areas of the Registry rather than the WOW6432Node. You will
get ICE warnings for this in an x86 package.
However you can't have one MSI which works natively for both x86 & x64
platforms.
An MSI has a platform attribu
Hi,
I'm facing issues while fetching the Installation Path of a 64-bit component
through its Registry Entry on 64-bit Platform. Through WIX, when I'm searching
for a particular registry key, because of registry redirection it is redirected
to WOW6432node where registry keys doesn't exist. So,
37 matches
Mail list logo
