1. Documentation in Burn is lacking. I personally still tend to optimize
fixing bugs over writing documentation. If find this to be optimal because
fixing bugs sometimes changes what the documentation would say.
You might argue that lack of documentation prevents people from finding bugs
(because
Thanks Peter! My intention is to prevent the install of per-machine msi until
the user uninstalls his per-user installation. Thanks for the pointers into MSI
API. I will take a look into that. Best,Martin> Date: Thu, 13 Oct 2011 11:01:00
+0100
> From: pshirtcli...@sdl.com
> To: wix-users@lists.
Hello:
I have an MSI developed with WIX, which packages (among other things) a
few .Net DLLs. Recently, these .Net v.3 DLLs have been updated to .Net
v.4.
I noticed that after running an upgrade, the .Net v.3 Assemblies remain
in the .Net 2 GAC (I noticed this after upgrades on Windows Ser
Hello Yan
I tried your test msi and it works fine as is on my machine, so it is going to
be environment.
The only other thing I could suggest you check is go to Sql Server
Configuration Manager (should be in the Program Menu) and check the protocols
being used - ensure that TCP/IP is enabled,
I know 3.6 is still under development, but documentation on Burn is
few and far between. I've long wondered if wouldn't be nice to have a
dumping spot to put some predefined templates. Ex: There are a lot of
common prerequisites (.Net frameworks, Visual C++ runtimes, SQL Server
CE, etc) that a l
Hi all,
I am generating patches using wixpdbs.
In this process does Wix tools need the location of the base version intacted??
In other words does Wix tools access the base version dlls/etc??
And what if in the same location I have build the newer version??
Thankx
Kanishk
--
Windows Installer doesn't support AppSearch on multi-sz.
On Thu, Oct 13, 2011 at 2:36 AM, Uma Harano wrote:
> Hi,
> I am performing an AppSearch for this string:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
> PendingFileRenameOperations.
> I am setting this value to a pr
Did the WiX documentation not help you? This case is explicitly called out.
On Thu, Oct 13, 2011 at 1:55 AM, Thomas Due wrote:
> Hello,
>
> I have a configuration application that I wish to run always after my
> installer have completed.
> I don't want to have the application start until I clos
Right now: use a built in variable or create custom BA that sets a variable
by reading the environment or create a custom BA and control the package
state more directly.
On Thu, Oct 13, 2011 at 6:13 AM, Sheehan, Andrew <
andrew.shee...@childrens.harvard.edu> wrote:
> Thanks Rob,
>
> Could you rec
Thanks Rob,
Could you recommend an approach that will work with element?
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Tuesday, October 11, 2011 4:52 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] InstallCondition he
Which per-user one ? There could be multiple per-user installations on a
machine.
You'd have to be an admin to detect the per-user installation of another
user. The other users might not be too happy if someone came along and
removed their installation if it had some user-specific
configuration/cu
Hi everyone, Is there a way to detect per-user installation and so that
per-machine install is prevented unless the per-user one is uninstalled first?
Thank you,
Martin Kulov
> From: mar...@kulov.net
> To: wix-users@lists.sourceforge.net
> Date: Tue, 11 Oct 2011 21:01:23 +
> Subject: Re: [
Hi,
I am performing an AppSearch for this string:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
PendingFileRenameOperations.
I am setting this value to a property called PENDING_RENAME.
I ran the setup then analyzed the msi log file. During AppSearch, I see this
entry in the
Something Dave probably didn't spot is that you're building from wixpdbs
whereas we are building from admin installations of MSIs. You've changed the
MSI but I'm guessing the codepage is coming from wixpdb which won't have been
changed.
You could build your patch from admin installations or maybe t
Hello,
I have a configuration application that I wish to run always after my installer
have completed.
I don't want to have the application start until I close the installer.
The application is installed into the INSTALLDIR location.
The custom action is defined like this:
And called whe
15 matches
Mail list logo