I have created a Wix installer for a 32-bit application (not .NET) which
installs just fine. Recently, I had to create a COM Server written in .NET
consisting of a single DLL which also had to be installed (and used by) my
original application.
So basically I wrote the COM server in C# (target
Thanks Rob, Is there a way to detect this situation and prevent the per machine
installation in such case? Thanks,Martin > From: r...@robmensching.com
> Date: Tue, 11 Oct 2011 05:56:50 -0700
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] major upgrade from per-client to per-mach
Burn doesn't resolve environment variables today. A verbose log file should
show you the condition being evaluated to true or false.
On Tue, Oct 11, 2011 at 11:57 AM, Sheehan, Andrew <
andrew.shee...@childrens.harvard.edu> wrote:
> Hi All,
>
> I've tried so many ways to get this to work but have
Yeah, I hate it when that happens. I had the same problem like 6 times this
year. :(
On Tue, Oct 11, 2011 at 7:25 AM, Simon Hoffmann <
vol714poursyd...@googlemail.com> wrote:
> Yeah, I'm actually planning to use Burn for the next major release
> after this one. I have been doing some testing and
Hi All,
I've tried so many ways to get this to work but have come up empty-handed.
Apparently I don't understand how the InstallCondition attribute works. I am
thinking that it will evaluate to either true or false, based on its
expression; but, I haven't wrote it correctly.
I have:
Yeah, I'm actually planning to use Burn for the next major release
after this one. I have been doing some testing and it looks very
promising, but for now, I'm afraid Burn's and our release schedules
don't align. ;-)
2011/10/11 Rob Mensching :
> Sounds like you might be best served by using a boo
Hi,
To support building patches against our old releases that were built with Wix
3.0. and now our release branches are being built on machines with Wix 3.5
installed.
So we have RTM msis from wix 3.0 these have codepage 0.
We now make an updated MSIs with wix 3.5 which now forces a codepage onto
Oh thanks, will try that, if I find out how (very new to this, really). So I
put that in deploy.proj right? And what do I have to do in my C++ code to
run it?
Really appreciate any help, thanks!
Rgds Leo
2011/10/11 David Watson
> We had this and had to run a step in our patch building scripts t
Hey there.
I created custom wpf window that displays messages for my BA. It is shown as
modal using ShowDialog() method. It does block BA thread, but not Engine
thread when pop-ups during, for instance, applying, so if user decides to
cancel installation he will see pop-up windows, but also not
It seemed to be right when I clicked install (caching?) so that makes sense.
It looks like the AV is more forgiving to signed exes so I might try signing
it with a test certificate to see what happens.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/
I always grab the binaries (we check them in) but still use the MSI for
Votive. I have VS2005, VS2008, and VS2010 but only need votive for 2010. So,
I don't install anything but the VS2010 integration.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/
We had this and had to run a step in our patch building scripts to set the
codepage to 1251.
See
http://msdn.microsoft.com/en-us/library/windows/desktop/aa369791(v=vs.85).asp
x
For the vbs file.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
S
Thanks for your reply!
Yes I read that but there are just too many Products in the package so in
the time frame it is not feasible. Perhaps trying to upgrade to 3.6 beta may
solve it? Will try.
2011/10/11 Rob Mensching
> Trying to create a patch across WiX versions is not supported. Patching is
Had a report of that a long time ago then it went away. Not sure exactly
what is triggering the antivirus. Unfortunately, the self extracting feature
in Burn looks a lot like what most viruses do so this isn't completely
unexpected...
On Mon, Oct 10, 2011 at 6:15 PM, jhennessey wrote:
> The last
What features are you selecting?
On Mon, Oct 10, 2011 at 6:04 PM, jhennessey wrote:
> Is there a way to extract the MSI then?
>
> The problem with providing just the exe right now is that it doesn't
> support
> installing only select features (like the MSI does).
>
> I was thinking that /layout m
Trying to create a patch across WiX versions is not supported. Patching is
very fragile and there are too many small changes in the tools that can
break patching.
That said, you may be able to get this to work by explicitly setting the
code page on your Products. It's possible the default in WiX c
Sadly, Windows Installer doesn't support that.
On Mon, Oct 10, 2011 at 9:23 AM, Martin Kulov wrote:
>
> Hi, (moving this to a new thread) I have an existing MSI that needs to be
> MajorUpgrade'd from per client to per machine installation.Right now
> installing the latest bits results in two ve
Sounds like you might be best served by using a bootstrapper/chainer.
On Mon, Oct 10, 2011 at 12:19 AM, Simon Hoffmann <
vol714poursyd...@googlemail.com> wrote:
> Hi there,
>
> I'm new to this list and am writing because I feel like im a Catch-22
> situation.
>
> I'm maintaining a WiX-authored MS
I am totally new to wix and have now a project in front of me using it.
Upgrading to Visual Studio 2010 means I had to try to upgrade from 3.0 to
3.5 of the wix package. I have solved some errors resulting from that, but
now I am stuck.
When a patch is compiled I get the following error:
error TRCH
-2147287037 = 0x80030003 = The path %1 could not be found.
Not sure what path it is referring to.
Does
C:\WINDOWS\Installer\{140A1F18-5BEA-4abc-8AD7-618FB595D207}\current\Setup.msi
exist or your scripts have access to it?
Dave
-Original Message-
From: maksim.vazhe...@emc.com [mailto:m
Hi All,
Recently on one host the installation started to fail with error 2203 when it
is being installed by a script; when I run the installation manually it runs
without any problems. Here is the complete verbose log:
=== Verbose logging started: 10/11/2011 0:57:06 Build type: SHIP UNICODE
21 matches
Mail list logo
