Hi
I recently had to do something similar, and ended up with 2 msi's. 1 for x64
and 1 for x86. I then wrote a small NSIS installer, that calls them and
installs them in sequence. Until burn is out, you have to ship 2 msis.
Cheers,
Leif
On Thu, Jun 17, 2010 at 3:49 AM, Sascha Beaumont
wrote:
> Y
Thanks guys for all your help. Here is what I ended up doing (probably
I had not framed my question right about what my requirement was).
Apologies if the explanation is naive, my experience/expertise with Wix
is not very sound.
- I had two MSI's. The first MSI dropped an exe on the hard d
Ahh... that sounds more a setup design problem ;)
I'm pretty sure I saw a thread recently about strange behaviour when
displaying additional InstallUISequence dialogs for configuration
after InstallExecuteSequence has completed. Sounds similar...
In my opinion you should gather configuration info
Hi Sascha - Thanks for the example code.
I understand the out-of-scope handle problem, and I don't save one and use
it for something...I just mentioned that in the previous post to see if it
made a difference during debug.
My code does work, until after install. I can log all day, but not aft
I'm using the following code (Sample code I found, not originally
written by me) which I haven't had any problems with. According to
msi.chm PMSIHANDLE objects are automatically closed as they go out of
scope, which doesn't happen for MSIHANDLE -- if you're using
MSIHANDLE you're required to close
Thanks for the reply, Blair.
Yeah, I just tried that for the heck of it... I would not ever do that in
production...
But the problem remains... I cannot log something late in the install
process...
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.co
Check the archives for more information, I asked a similar question
sometime last year. I can't find the exact thread, but ended up being
convinced to make the change. I did however find a list of pointers
from Rob around localization - changing the PackageCode was important
enough to be item 0 ;)
You'll need to ship two separate MSI files if you want to do this
using Windows Installer.
On Thu, Jun 17, 2010 at 5:57 AM, Blair wrote:
> It is by design of Windows Installer.
>
> -Original Message-
> From: David Watson [mailto:dwat...@sdl.com]
> Sent: Wednesday, June 16, 2010 8:41 AM
>
This works for me:
True
.NET Framework 4.0
True
> -Original Message-
> From: Jason Ding [mailto:jas...@geo-slope.com]
> Sent: Wednesday, June 16, 2010 6:51 PM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Inst
I am tring to use Bootstrapper to install .Net Framework 4.0 by using a sample
from this site:
http://wix.sourceforge.net/manual-wix3/install_dotnet.htm
I got a message like this:
warning MSB3155: Item 'Microsoft.Net.Framework.4.0' could not be located in
'C:\Program Files (x86)\Microsoft SDKs\
That worked perfectly. Thanks!
Andrew
On Tue, Jun 15, 2010 at 3:40 PM, Blair wrote:
> If your base XML file (as shared by all three products) is fairly static,
> you should be able to create a shared component (a component where the GUID
> and the directory are the same for all three products).
You must always use the handle supplied to you from the entry point (custom
action function) into your DLL. Do not ever save it for a different entry
point, because it may not be valid in other calls or any time after code
returned back out the entry point it was supplied to you on. If you have
mul
Depends on your servicing strategy. Keeping the same ProductCode for two
different languages can compound small update component rule upgrade
violations if packages from two different languages were ever to be applied
to the same computer, and considering that you can change a computer's
language s
It is by design of Windows Installer.
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: Wednesday, June 16, 2010 8:41 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Setting Permissions on a 64 bit system folder from a 32
bit msi.
Hi,
I have a similar problem, and I see this message was ignored by the
community. Maybe it is a stupid question? I dunno - but I have the problem
too.
I noticed my MSIHANDLE is one ('1') before installation of the files. AFter
the files are installed, the MSIHANDLE is eight ('8').
Before install
I've wrote a XSL transform once to add the element for the
responsible for the exe. That was not pretty. Much easier to use
the XSL transform to exclude the as Neil suggested. Depending on
your heat command line you might need to exclude the and a
.
Edwin G. Castro
Software Developer - Sta
Oops, I just noticed you answered you're own quest. also != does not work for
conditions, its <>, like you have. My bad.
greenaj
Michael Clark wrote:
> Sorry as usual I figured it out on closer inspection I needed to make the
> following adjustment
>
>Value="InvalidUserDlg" Ord
I've been burned by this to. All of the conditions for SpawnDialog/NewDialogs
must be mutually exclusive. Do no be deceived int thinking that they execute
in the order specified by @Order. Have for the
SpawnDialog and For NewDialog. If your property is
set to a numeric value, you shouldn'
For the .net component you could apply a XSL transformation to the file
heat generates - heat will even apply it for you.
For the service you could do the same but it might be easier to script
the service code and file install and use the XSL transform to exclude
this file from you harvested code.
Ok I didn't realise that either. Mandar, ignore me you'll have to do it
the hard way :-)
Neil
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: 16 June 2010 07:25
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Detecting MSI dependencies
T
Hi,
I was going through an example for localization and came across this MSDN
page http://msdn.microsoft.com/en-us/library/aa372369. It says that we must
change the productCode for every localized package. Is this a necessary
condition or just a good practice? I'm planning to create MSIs for diffe
I am trying to work through some automation scenarios regarding heat and
some file-dependent Components. Here is the scenario... I have a product
that consists of a set of .exes and dlls. I would like to use heat.exe to
automatically generate these deliverables for me at build time. It does
this
Hi,
I am trying to set permissions on a folder under system32 on
64bit windows in a 32 bit msi. I know this is not great from a security
perspective but it's currently a requirement of the application. We wont
use the everyone account in the real installer.
Like so...
Sorry as usual I figured it out on closer inspection I needed to make the
following adjustment
-Original Message-
From: Michael Clark [mailto:mcl...@fullarmor.com]
Sent: Wednesday, June 16, 2010 9:36 AM
To: General discussion for Windows Installer XML toolset.
Subject: [Wi
I have the following UI sequence
1
1
VALIDUSER = "0"
1
I also tried
In the ValidateUser function I return 1/0 based on if the user name and
password are validated, and I want to Display the invalidUser dialog if the
value is 0.
I have validated in the log tha
On 6/15/2010 4:33 AM, Óscar Alberto wrote:
> I have created a msi with customized bitmaps (the company logo and all
> that stuff). While doing a normal installation, the images looks good;
> the problem comes when I try to make a patch: the msp file continues
> using the default bitmaps.
>
Che
Hi,
Cloud you please provide more information about Bootstrapper according
to UAC.
What step should I do ?
Thanks,
Aun.
On Wed, Jun 16, 2010 at 1:27 PM, Blair wrote:
> The short answer is: Bootstrapper. You need one.
>
> UAC is probably the reason your getting a failure in Win7.
>
27 matches
Mail list logo
