I have a similar situation where I am building two different WIX burn chainers
(long story, has to do with .Net versions). In any case I was running into
similar issues with the paths. I ended up creating an environment variable for
my Wix 3.6 binaries path and inserting that in my WIX files a
Perhaps the developer meant certification of the application (i.e. Windows 7
App Certification), rather than requiring a certificate?
Andreas A. Mertens
Founder, Software Consultant and Developer
NVision Ideas, Inc.
email: andre...@nvisionideas.com
Fr
> possible docs I found absolutely nothing. If any this will be
> probably at
> the msi level anyway since WIX schema does not have anything
> closely
> similar.
> Regards and thanks for your reply!
>
>
> -Original Message-
> From: Andreas Mertens
> S
runs that.
Of course you still need a core launcher app to deal with, but overall I find
this works reasonably well.
Andreas Mertens
NVision Ideas Inc.
- Original Message -
From: Mark Turek
Date: Friday, February 4, 2011 1:28 pm
Subject: [WiX-users] bypass fileinuse
> I have a req
OFF-TOPIC - this has to do with compilers and manifests, but does refer to
this problem.
I have experienced a similar issue with a client's product I was working on.
With VS 2008 SP1, a new revision of the C runtime/ATL/etc. DLLs are used.
Apps compiled with this will have this registered in thei
I had a similar situation as well.
I used Microsoft's Bootstrap generator app to create bootstrapper from my
installer. But it changed the case to all lower-case, even though the
HomeSite URL still had the mixed case format. When this was installed to a
*nix-based web server (not sure what the c
Just a guess, but in seeing that the registry entry is in the Installer
area, I am wondering if in the IS install if these private assembly files
are marked as the KeyPath, which is why they are being recorded here?
As far as the crashing is concerned, have you confirmed if your private
assembly f
oyer). It isn't
something that either Windows Installer or WiX currently has.
-Original Message-
From: Andreas Mertens [mailto:andre...@nvisionideas.com]
Sent: Friday, November 13, 2009 5:01 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users]
and IE8 when updating an
add-on
This was code we added on especially for IE. There isn't anything in WiX or
Windows Installer to do that natively.
-----Original Message-
From: Andreas Mertens [mailto:andre...@nvisionideas.com]
Sent: Thursday, November 12, 2009 5:57 PM
To: 'General d
them
all to the RM session (in the case of Vista+) or offered to the user to kill
them (in the case of XP/2k3).
-Original Message-
From: Andreas Mertens [mailto:andre...@nvisionideas.com]
Sent: Thursday, November 12, 2009 5:51 AM
To: 'General discussion for Windows Installer XML too
ke a bit longer to
get resolved there...
Thanks,
Andreas Mertens
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus
be
superseded by the All Users install. Either way I could still run the
installed product. I could later uninstall my installation and still have
access to the All Users installation.
Does this make any sense? Are there any drawbacks to this thinking?
Thanks,
Andreas Mertens
-Original
I have been following this thread (as it has a definite impact on what I am
working on).
Searching through the online MSDN docs, I came across the following that
describes Per Machine/Per User installs and the impact of the ALLUSERS
variable. It has also been updated with the Windows 7 details.
h
27;t want users to be presented
with the prompt to verify admin credentials when doing a PerUser install.
In fact a non-admin should not get the choice in the InstallScopeDlg (just
as in XP).
3) If UserA (admin) does do a PerMachine install, then installations by
later user
the best way of including the "FilesInUse" dialog (and the
"MsiRMFilesInUse" dialog as well I suppose) so that it show up if necessary
in the .MSI
2) If the dialog is added in step #1 above, will it be available when I
apply the patch?
Forgot to mention - this is with Wix 3.0 RTM (D'oh) :)
Andreas
-Original Message-
From: Andreas Mertens [mailto:andre...@nvisionideas.com]
Sent: October-24-09 7:57 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Installation to limited user account faili
uld be happy to hear any suggestions on doing this
better.
Thanks,
Andreas Mertens
--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year.
I took a look at vs_piaredist.exe, and found you can extract the .cab or
.msi from it (using WinRAR or other such tools). Perhaps you can just grab
one of those and package that up in your install?
Andreas Mertens
-Original Message-
From: John Hall [mailto:john.h
I am new to Wix, but I have done something similar myself. My opinion is to
take that huge feature and identify the various component "groups" (related
functionality). Create a separate .wxs file for each such group of
components and move them into that. Create in each file a single Feature
elem
part of the path.
Andreas Mertens
-Original Message-
From: Richard [mailto:legal...@xmission.com]
Sent: August-07-09 11:05 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] merge modules for C++ runtime (2005/2008) with
ATLsecurity fix?
In article ,
"Alex Iv
20 matches
Mail list logo
