Hi All,
I am having a very annoying problem. I have a managed bootstrapper application
which requires .Net 4.5. I have the proper PackageGroupRef in my bundle's
chain, and it installs .Net 4.5 successfully when there is no .Net installed.
The problem is that if .Net 4 is already installed I
I'm currently porting a Visual Studio setup and deployment project to WiX.
Part of the setup is to install a COM+ Application with a specific COM+
component that has a bunch of interfaces and methods.
My problem is that when i specify the native (C++) DllPath and specify one
single
Hello!
I'm have got wix 3.7 integrated into daily builds in my company (build machine
OS is Windows XP). It used to run fine, scripts were invoked properly with ANT
and burn bundles were created until some time ago I started to observe some
build crashes (most of the time it builds correctly
Please remove me from the Mailing List
Ian Pender | Desktop Developer
Huddle - Collaborate intelligently
ian.pen...@huddle.commailto:ian.pen...@huddle.com | +44 (0)203 598 1564 |
www.huddle.comhttp://www.huddle.com/ | @huddle
London | New York | San Francisco
On 24/04/2013 10:01, Kagiso Seboni wrote:
Please remove me from the Mailing List
You can unsubscribe via the mailing list interface at:
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Bruce Cran
--
Try New
Hello,
Today we have a bootstrapper, taking care of first installing .NET 4.5, and
then the MSI with the application. If the user runs Windows XP, or any
OS/Sp-levels not supported by .NET 4.5 the installation fails with a
error-code.
How do I add a condition in the beginning of the
Use the Bundle/@Condition attribute. It was designed for this scenario.
On Wed, Apr 24, 2013 at 3:25 AM, Sam Boman s...@samb.se wrote:
Hello,
Today we have a bootstrapper, taking care of first installing .NET 4.5, and
then the MSI with the application. If the user runs Windows XP, or any
It's very possible the COM+ CA in WiX toolset doesn't do exactly that.
Perhaps you could take a look at the code and see what is wrong? Code is
in src\ext\ComPlusExtension. I know nothing about COM+ so I'm not much help
beyond that.
On Wed, Apr 24, 2013 at 12:04 AM, Bart van Lierop
What version of the .NET Framework are you using? It certainly could be a
bug. Not many people use Windows XP as a development box any longer so we
might not get much coverage there.
On Wed, Apr 24, 2013 at 12:18 AM, Pawel Fujcik pfuj...@proximetry.plwrote:
Hello!
I'm have got wix 3.7
.NET Framework 4.0
Od: Rob Mensching [r...@robmensching.com]
Wysłano: 24 kwietnia 2013 14:29
Do: General discussion for Windows Installer XML toolset.
Temat: Re: [WiX-users] Light.exe error while running build on build machine
What version of the .NET
Ahh, there were some screwy issues under WiX v3.7 and friends where NETFX
2.0 (or NETFX 3.5 if you prefer) was necessary to have the toolset build
fully. We didn't catch it because most OS's have NETFX 2.0 or 3.5
pre-installed and we thought that NETFX 4.0 clean would work.
Try adding NETFX 2.0
Unfortunately, this is not the problem because NETFX 2.0, NETFX 3.5 and NETFX
4.0 are already installed on build machine (our projects target NETFX 4.0). It
must be something else.
Od: Rob Mensching [r...@robmensching.com]
Wysłano: 24 kwietnia 2013 14:39
You can unsubscribe via the mailing list interface at:
https://lists.sourceforge.net/lists/listinfo/wix-users
-Original Message-
From: Kagiso Seboni [mailto:kagisoseb...@yahoo.com]
Sent: April 24, 2013 02:01
To: wix-users sourceforge
Subject: Re: [WiX-users] REMOVE ME PLEASE
Please
We have a WiX (.msi) installer that has to run as administrator, but at the
end a service app is needed to be launch, but has to launch in non-elevated
mode. If it is launched in elevated mode then users have to restart the
machine to have it launched in non-elevated mode.
Now we have a dll that
Is there anywhere where I can see an example of this? I tried using the same
condition I have for .Net 4.5 and it still skips the prereq and tries to run
the BA. Also, what is the correct syntax for the BootstrapperCore.config for
.Net 4.5? If I use 'supportedFramework version=v4.5 /' the
Why did you put stable between asterisks? Is there a caveat? What does it
mean?
Or use Heat with the -ag switch to make it generate *stable* GUIDs.
--
View this message in context:
That's standard in Markdown to mark a word with *emphasis*.
On Wed, Apr 24, 2013 at 7:19 AM, sleon sergioleonc...@gmail.com wrote:
Why did you put stable between asterisks? Is there a caveat? What does it
mean?
Or use Heat with the -ag switch to make it generate *stable* GUIDs.
--
View
The WiX documentation has a topic about launching an executable at the end
of install. Unless you explicitly launched your installation elevated, it
will launch as the normal user.
On Wed, Apr 24, 2013 at 6:42 AM, TimM timmay...@smarttech.com wrote:
We have a WiX (.msi) installer that has to
Shortly after I posted this yesterday, I figured out the problem. I am
trying to customize the built-in dialog for installing the .NET dependency.
From my earlier post:
Page Name=Welcome
Hypertext Name=EulaHyperlink X=552 Y=366 Width=-11
Height=34 TabStop=yes
The src\ext\bal\wixstdba\WixStandardBoostrapperApplication.cpp has a table
of identifiers at the top of the code that connect it to the theme.
On Wed, Apr 24, 2013 at 7:46 AM, mvd1 ma...@costar.ca wrote:
Shortly after I posted this yesterday, I figured out the problem. I am
trying to
On a 64 bit OS you'd probably want a second search with Win64=yes.
Property Id=EXCELPATH32
RegistrySearch Id=ExcelDirSearch32 Root=HKLM
Key=SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\excel.exe Type=raw
/
/Property
Property Id=EXCELPATH64
RegistrySearch Id=ExcelDirSearch64
thanks for the reply Jacob. Will try it out tomorrow when in office.
I also found that the same works on a 2010 version of office (32 64 bit, on
64 bit OS). One would have expected it to fail on that too, but it works there.
From: Hoover, Jacob
Why sir, surely if it is in verbal jousting that thoust taketh part, thou
should be sharpening thy lance and not thy sword.
- Original Message -
From: Rob Mensching r...@robmensching.com
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Sent:
Hi,
If I change the install location (InstallFolder) to a non-default value, and
the Bundle then needs a restart (.NET 4.0 installation), the value after
reboot is back to the default value.
I've tried setting Persist=yes but that makes no difference..
Is this a bug?
Is there a workaround?
Persisted='yes' worked for the Visual Studio installer, I know they use
this extensively.
On Wed, Apr 24, 2013 at 9:37 AM, rowbot james.row...@microfocus.com wrote:
Hi,
If I change the install location (InstallFolder) to a non-default value,
and
the Bundle then needs a restart (.NET 4.0
Hello,
I'm noticing quite an awkward problem with the dotnet 3.5 installer.
Specifically, it appears to wipe out hkcr\installer\dependencies when a user
performs a repair.
I am using wix dependency extension and this is causing something of a problem
on a few Xp machines (which
Can anyone help me with this?
Nick
-Original Message-
From: Nick Miller [mailto:nmil...@livetechnology.com]
Sent: Wednesday, April 24, 2013 2:08 AM
To: General discussion for Windows Installer XML toolset.
(wix-users@lists.sourceforge.net)
Subject: [WiX-users] Trouble with DotNet
Hi
I'm new to WiX so my apologies if this is something I should know already.
Background:
I'm trying to use WiX to implement a new installer for an existing product
whose current installer was written using a commercial tool. We have a large
library of functions that our current installer calls
Hi, I am a little lost and wondering if anyone knows how to prevent a minor
upgrade. Major upgrades are working fine. What I want to achieve is to prevent
(or at least deter through UI) minor upgrades. Does anyone know the conditions
for detecting them?
Hi Greg,
If I understand your problem correctly, what you need to do is add these dll's
as references to the custom action project, then set the Copy Local property to
true. When you build the custom action, your customaction.CA.dll will contain
all of the dependencies needed for it to run,
Okay, just now got a chance to get back to this.
To recap, the issue am seeing is as follows:
If I install the msi directly, and then uninstall the msi from
ARP, the UILevel is 3 during the uninstall of the .msi. I
verify this by checking the value of the UILevel property with a custom action.
Nick, thanks for the reply.
I'm importing the old DLL into my custom action DLL using DllImport(),
because Visual Studio won't allow me to add it as a reference to the
project. I'm not entirely sure why, but I suspect it is because the old DLL
is unmanaged code (written in Delphi 2007). I'm
Stupid question I know...
I am using WIX 3.7 and using burn to bootstrap my MSI's
Most of my MSI's have no need to show UI, so in Burn i am using:
DisplayInternalUI=no
I have quite a few DTF Custom Actions, and I am using:
Most are Message failures in try catch exception:
catch (Exception ex)
Hi Greg,
I had one other idea, you might be able to include your unmanaged dll as an
embedded resource and have the CA copy it to a temp directory, then reference
it from there. It's a quick and dirty way to get it done, but it should work.
Basically it would look like this:
private void
Interesting idea. I'll try that tomorrow when I get back into the office.
Quick and dirty is fine with me, and if that works then it'll do.
I also came up with another possibility, which is simply to write another
installer that would install the DLL to a known location. This little
installer
On 24-Apr-13 20:54, GregS wrote:
Of course, the right thing to do would be to convert that old DLL into a
true custom action DLL. I'm going to look into that tomorrow, too. Hoping
it's possible and doable in the time available. Not sure how good the
support for MSI is in that old version of
On 23-Apr-13 13:24, David Kauffmann wrote:
I would really love to see an extension to the WixUtilExtension library
which provides an EventLog element with the Attributes
ModifyOverflowPolicy, MaximumKilobytes, MinimumRetentionDays...
essentially all the Properties you can set for an EventLog
37 matches
Mail list logo
