Actually, trying my idea didn't work for me. It may not be possible to have a
single patch file that updates multiple versions. However, you may be able
to create a patch for each version that you want to update. For each one,
keep the PatchFamily's Id the same (that way they'll maintain their corr
On 13-Jun-13 08:11, Bruce Cran wrote:
> the system will reboot but the installer doesn't run again. Running it
> manually causes the progress bar to appear immediately and installation
> continues, so it seems it's just missing the RunOnce entry to start it
> after login.
Do you see if the entry's
On 18-Jun-13 06:13, Barrie Cooper wrote:
> All works fine on my development and testing environment but on my client's
> laptop yesterday we received an error stating "0x800703E9 Recursion Too Deep"
> during the SQL Server installation.
From SQL Server or Burn? Please post the exact error messag
On 23-Jun-13 15:13, Ivo Beltchev wrote:
> I need an installer that can work for both 32-bit and 64-bit OS. Currently I
> build 2 separate MSIs and bundle them together in a bootstrapper EXE. The
> problem is that 90% of the files are common between the two platforms and my
> installer is almost dou
I haven't tried it, but could you add a PatchFamily for each version that you
want patch? Each PatchFamily would have a Version to identify the product
version to update. You would not use the PatchFamily's ProductCode attribute
at all. Instead, the parent Patch element's TargetProductName would ma
Ah, ok. Well, if the main thing is to get the size of the install, would
using Burn's download capabilities add anything for you (using the
DownloadUrl attribute on your Burn MsiPackage elements)? Such as only
downloading the 64-bit installer if that's what they need, or only the
32-bit one? Of cou
It is a shell extension. I need to register both 32-bit and 64-bit DLLs when
I install on 64-bit OS. Also I would prefer on 64-bit systems to install in
the main Program Files, where all self-respected applications supporting 64
bits should go.
-Original Message-
From: Nick Ramirez [mailto
Yes putting the .NET installer in the "redist" sub-folder works! This is also
confirmed by looking at the WiXNetFxExtension source code. Thanks!
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Friday, June 21, 2013 4:15 AM
To: General discussion for Windows
Since I have not done this myself, can you say how you are referencing .wxl
files for a custom BA? Are you saying that you're using WiX localization
variables in a Windows Forms app?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Localizatio
Yes, you are right, I just found the key
HKLM\SOFTWARE\Wow6432Node\Microsoft\DevDiv\vs\Servicing\11.0 on my 64 bit
machine.
Can you recomment some books or website which can help avoid this kind of
tricks. Is <> ok? I know the ansser may be wide-ranged and
hard to be specified to a certain ma
You mention wanting to detect whether Visual Studio is installed. Are you
installing an extension for Visual Studio? If so, have you looked into using
a VSIX package installer?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Can-t-understand-util-
I'm often curious to learn more about 64-bit vs. 32-bit applications. What
are your reasons for targeting both architectures? Is it not possible, in
your case, to only target 32-bit? You say that there are 10% of files that
are different between the two installers? Can you say more about that? Does
What I meant by this is I create 2 separate MSIs then use torch to create
MST that transforms one into the other. I found this suggestion when
searching for a solution to my problem (might have been on stackoverflow). I
am still not 100% sure if this is indeed not possible or I did something
wrong.
Classification: Public
Hi Ivo,
I am not really sure on your overall question...
However, you cannot create 1 MSI for both 32 and 64 Bit OS's there must be 1
MSI for each bitness (32/64).
So this paragraph is not possible:
" One solution I tried is to create a transform that converts one MSI into
Hi.
I need an installer that can work for both 32-bit and 64-bit OS. Currently I
build 2 separate MSIs and bundle them together in a bootstrapper EXE. The
problem is that 90% of the files are common between the two platforms and my
installer is almost double of what it can be.
One solution
Classification: Public
If you create a x86 (32 bit) MSI it will install to c:\program files (x86)\
folder on a 64 bit OS If you application is 32 bit, it should not install to
c:\program files\ on a 64 bit OS, it should go to c:\program files (x86)\
-Original Message-
From: Blair Murri [
16 matches
Mail list logo
