Hi,
As you know and as posted in the article below, WiX v3 has moved to .NET
Framework 2.0 while WiX v2 will stay on .NET Framework 1.1 SP1.
http://robmensching.com/blog/posts/2007/12/7/wix-v3-on-the-.net-framework-2.0-eminent
However, I did not find much information on the plan of .NET Framewo
Hi,
As you know and as posted in the article below, WiX v3 has moved to .NET
Framework 2.0 while WiX v2 will stay on .NET Framework 1.1 SP1.
http://robmensching.com/blog/posts/2007/12/7/wix-v3-on-the-.net-framework-2.0-eminent
However, I did not find much information on the plan of .NET Framewo
good thing!).
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-----
From: Jun Yin [mailto:jun...@microsoft.com]
Sent: Tuesday, February 25, 2014 11:34 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Suppress bund
fsetup.com]
Sent: Monday, February 24, 2014 8:01 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Suppress bundle caching and registration in ARP
On 24-Feb-14 20:41, Jun Yin wrote:
> Is it possible to suppress bundle caching and registration in ARP (Add/Remove
> Program
Is it possible to suppress bundle caching and registration in ARP (Add/Remove
Programs or Program and Features).
If I set attributes DisableModify="yes" DisableRemove="yes"
DisableRepair="yes" and attributes Cache="no", it seems that
* ARP entry is still written to the registry
HKEY
By reading the source code of StdWixBA.dll, I found that StdWixBA.dll could
optionally load bafunctions.dll for extension.
HRESULT LoadBootstrapperBAFunctions()
{
HRESULT hr = S_OK;
LPWSTR sczBafPath = NULL;
hr = PathRelativeToModule(&sczBafPath, L"bafunctions.dll
in
select 3.8 from the dropdown and then it should say wix38rtm v3.8.1128.0 as of
commit 3a144292ea18, Nov 28, 2013 click the commit and then click download
-Original Message-
From: Jun Yin [mailto:jun...@microsoft.com]
Sent: February-21-14 5:40 PM
To: General discussion about the WiX
ad the Exe, and run it to install Visual Studio Integration, then use the
New Project Wizard to Create A VS Project that you use for your own project.
Carter
Quoting Jun Yin mailto:jun...@microsoft.com>>:
> Hi,
>
> I downloaded WiX toolset v3.8 from
> https://wix.code
Hi,
I downloaded WiX toolset v3.8 from
https://wix.codeplex.com/releases/view/115492 and installed the EXE and unzip
the ZIP.
However, when I try to open the WiX solution file: E:\wix38-debug\src\wix.sln
with Visual Studio 2010 or Visual Studio 2013, the following errors:
E:\wix38-debug\src\t
In wix38-binaries package, it seems that only the x86 platform version of
Burn.exe is provided (under wix38-binaries\x86 directory).
I am wondering if an ARM platform of Burn.exe would be provided too. If not,
are we allowed to compile one using the source code under wix38-debug\src\burn?
Thank
and binding, and #() is
resolved at runtime.
2. The latter.
-Original Message-
From: Jun Yin [mailto:jun...@microsoft.com]
Sent: Monday, January 27, 2014 5:04 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] !(loc.XXX) or #(loc.XXX)
In WIX, localization strings are referenced
In WIX, localization strings are referenced using the !(loc.xxx) syntax, and
defined in WXL files:
http://wixtoolset.org/documentation/manual/v3/howtos/ui_and_localization/make_installer_localizable.html
However, I find to enable localization strings in a bundle using WIX standard
bootstrapper
I am trying to create a simple Bundle with a few MSP patches using WIX and
Burn. According to the documentation, it seems very straight forward, like this:
http://schemas.microsoft.com/wix/2006/wi";
xmlns:bal="http://schemas.microsoft.com/wix/BalExtension";
xmlns:util="http://schemas.microsoft
13 matches
Mail list logo
