I think you'll find that SQL 2008 requires .NET 3.5 to be installed (SQL
2012 will work with .NET 3.5 or 4.0).
Neil
>I'm creating a Bundle that installs the .NET Framework 4 and then SQL
>Server Express as needed. The Chain element looks as follows:
>
>
>
>
>
>
>
>
I'm in a similar situation with close to 30,000 files to deploy of which
perhaps 50 - 100 are DLL's, EXE, OCX etc.
I've ended up grouping files together in a component, (with the exception of
DLL's etc) sometimes up to 5,000 or 6,000 in one component. I also forced a
version number for each fil
On 29-Jan-13 17:39, Eric Schultz wrote:
> If .Net Framework 4 is already installed, SQL Server installs fine. If .Net
> Framework 4 is not installed, the SQL Server Express install fails because
> it says the .Net Framework is not installed. In fact, it says it needs the
> exact same version as was
On 28-Jan-13 16:24, John J. Hughes II wrote:
> I have searched the web for " Error 2896 " which seems to say it is a UAC
> problem but I also found references that say WixShellExec which prompt if
> need for UAC permission so I would not expect that to be a problem but I am
> new to the toolset.
Ho
On 25-Jan-13 10:44, Hoover, Jacob wrote:
>I currently have a single MSI with ~30k components. During installations
> and major upgrades it appears the sheer number of components is causing
> performance issues (the files are data files so there aren't version info
> headers). What is the bes
On 29-Jan-13 16:10, Karl Werner wrote:
> However, still stuck on the original problem -> How can I get the MSI's UI
> invoked on the second run of the bootstrapper.
You can't. Burn needs to know the operation being performed which it
can't if the operation is determined during the execution of the
I have installed my product and it works like a charm...
I have modified my install to work with Repair since I have a lot of custom
actions and 5 merge modules.
When I run repair all is good EXCEPT all files are being installed in 1
folder I have 5 folders:
C:\Program Files\MYCORP\MYCORP Servi
One of my partners was kind enough to post an Elance job to help entice someone
to demonstrate to how tackle my earlier question with WIX. The direct link
is...
https://www.elance.com/j/dynamic-wix-installation-package/37325289
Anyone interested?
-- G. Deward
Begin forwarded messa
I'm creating a Bundle that installs the .NET Framework 4 and then SQL
Server Express as needed. The Chain element looks as follows:
If .Net Framework 4 is already installed, SQL Server installs fine. If .Net
Framework 4 is not installed, the SQL Server Express inst
So if I use different upgrade codes, defined using pre-processor variables,
then that should prevent the problem in all cases, I suppose.
However, still stuck on the original problem -> How can I get the MSI's UI
invoked on the second run of the bootstrapper.
On Tue, Jan 29, 2013 at 2:23 PM, Hoov
But if they run the downloaded bundle a second time it would, I believe.
-Original Message-
From: Karl Werner [mailto:karl.wer...@gmail.com]
Sent: Tuesday, January 29, 2013 1:38 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Redisplay MSI's UI when B
Since the bootstrapper isn't registering itself in ARP, that shouldn't
matter, right?
On Tue, Jan 29, 2013 at 11:24 AM, Hoover, Jacob
wrote:
> But if the same component is used in both the 32 bit and 64 bit MSI, a
> repair or removal is going to find InstallCondition=true for both packages.
>
> -
But if the same component is used in both the 32 bit and 64 bit MSI, a repair
or removal is going to find InstallCondition=true for both packages.
-Original Message-
From: Karl Werner [mailto:karl.wer...@gmail.com]
Sent: Tuesday, January 29, 2013 11:12 AM
To: General discussion for Wind
While I'm still stuck on the core issue here of not being able to redisplay
the UI from the bootstrapper, I thought I'd document another way around the
ancillary uninstall issue:
Add a ComponentSearch for a component that the msi's will install:
Then set the InstallConditions similar to this:
So I populated the UpgradeCode using a pre-processor variable and use a
different code in the build properties for the x86 vs. x64 projects. This
seems to fix the uninstall issue.
Now back to how to re-display the MSI's UI on subsequent runs of the
bootstrapper?
Thanks!
Karl
On Tue, Jan 29, 20
Ah, that makes sense and may be what is causing the 32-bit msi to be
executed with uninstall. I'll look into how to fix that. Any ideas?
It does not however explain why the MSI's UI is never displayed . . . Even
if I take the InstallCondition out along with the second MsiPackage, I
still don't
My guess would be because you are sharing UpgradeCode. When burn runs a second
time, the 32bit MsiPackage is going to detect based on upgrade code. Because
your InstallCondition evaluates to false, it schedules the removal of it.
-Original Message-
From: Karl Werner [mailto:karl.wer...
There appear to be 2 distinct problems here:
1) MSI's UI is not redisplayed on subsequent bootstrapper execution.
2) Install Conditions are not behaving as I expect.
I've discovered that the uninstall is happening because I have two msi
packages, one for 64-bit, and another for 32-bit. These msi'
Currently we have a Wix Bundle that provides minimal interaction through a
custom .Net UI. We don't have the Bundle name set so the bootstrapper
won't get registered in ARP (by design). It then chains some pre-rquisites
and our product. Our product is an MsiPackage, something like this:
There are other ways you could do it but if you've been told how to implement
the requirement too, there's not much point going into it. To answer your
question...
Creating a process to make a Wix installer automatically is just the same as
making any automated build. If you use Votive (Wix Visual
Your best bet is to create a custom action
i.e. I close Outlook at the beginning of the install, then relaunch it after
the install (if Outlook was indeed closed)
///
/// Kills Outlook just as the install/uninstall starts
///
///
/// return ActionResult
Hi,
Can anyone please help me to detect any running process through WIX and ask
user to close it?Following code is detecting the installed application is
running during "repair". But it was not working to detect Internet Explorer
during "installation".
Please also provide the po
I have a msi file that has many transforms defined in it.
When I use the msiexec.exe to install a transform the instance installs.
Example :
Msiexec.exe /i l:\mywixproject\Setup\Dvd\MyProj.msi MSINEWINSTANCE=1
TRANSFORMS=:MyProject1 INSTALLFOLDER=”c:\myProject” INSTALLLEVEL="20"
ARPSYSTEM
Unfortunately, based on our current requirements, we must not prompt the user
in any way nor may we require them to download a second file. Our client has
requested that certain customer-specific variables be known by the application
during install. The application must supply these variables
If your MSI packages are always the same apart from that single configuration
file, one way to do it would be to exclude file from the MSI. Then create a
single, static MSI and let the application download the config file at
runtime and configure itself, if it hasn't already done so.
This would be
Is it possible to use Wix to programmatically create an MSI Installer using a
background process and an existing file structure? I would like to embed a
customized configuration file within their downloadable installation package.
I have never used Wix so any links to code or samples, demonstr
I spent some time becoming acquainted with the burn engine source, trying to
figure this one out.
Unless I'm missing something (which is entirely possible) it seems to me that
Burn's dependency mechanism doesn't handle Major Upgrades at all. There are two
situations that cause a problem:
Bundl
27 matches
Mail list logo
