The FirewallException implementation seems to only allow a single port number
in the port property.
I need to open a block of ports for a custom service exe. I don't want to code
up 100 invocations of FirewallException, one port at a time.
How do I specify a port range?
I used heat.exe to generate a .wxs file that lists all the files that I want
to install. I told heat to put them in a ComponentGroup so I could
reference them from another (hand-generated) .wxs file.
However, the autogenerated file specifications look like this:
Component
commandline or msbuild?
On commandline you can add -gg to generate guid's when heat is run, or -ag
to use * instead.
With the msbuild task I use this: GenerateGuidsNow=true to generate them.
I use msbuild, and have heat setup like this:
HeatDirectory
Thanks John.
After a bit of frustration I finally figured out my issue, it was one of my
conditions on the publish events that was screwing me up. Now that I fixed
that I can correctly enter 1 to 5 numbers and have it do what I expected it
to do
--
View this message in context:
Cool. What publish event condition did you use? Always something to learn.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
I believe, and someone can correct me if wrong, that generally the
WixFirewallExtension supports the parameters which were available to the
Windows Firewall (XP era) which also works with the Windows Advanced
Firewall. But the extension does not provide a way to specify some of the
parameters of
I was actually using a PORT_NUMBER 0 conditions before I switched to
MaskedEdit and therefore once I switched I did not remove that condition as
the mask # does not accept negative numbers and therefore I did not need
that condition. Once I removed it then it began to work as expected.
--
I have seen many WiX articles on detecting .NET 4.5 or greater and I have
implemented the recommended entires, but my install will FAIL to detect .NET
4.5 on machines that have .NET 4.5 and 4.5.1.
Now we are still using WiX 3.7, and therefore if the machine has .NET 4.5.1
does the NETFRAMEWORK45
Probably not but it would be awesome if someone helped add that support.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Phill Hogland
You have the check the registry.
Here is my example but with .NET 4.0
!--.NET 4.0 Installation detection--
Property Id=NETFRAMEWORK40CLIENT
RegistrySearch Id=NetFramework40Client Root=HKLM
Key=SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client Name=Install
Type=raw /
/Property
From the Wix 3.8 wix.chm documentation:
Here is a complete list of properties for the .NET Framework 4.5 and .NET
Framework 4.5.1 product families. Note that because v4.5.1 is an in-place
upgrade to v4.5, the same properties are used for both versions. To
differentiate, you must check the
So, what does your condition look like? Can't see it in your authoring.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From:
I upgraded from 3.8.1128 to 3.9.702 a few days ago, and I am observing a
change in behavior in the why my bundles are updated. (I am aware that
there are new features in 3.9 related to bundle updating, but was not
expecting this behavior change. At the same time I did not revert my build
system
Pre-processor loop
?portRangeList=1,2,3,4,5,6,7,8,9?
?foreach dynaPortAwesomeness in $(var.portRangeList)?
fire:FirewallException Id=MyFirewallException
Name=!(loc.CASFirewallExceptionDescription) Port=$(var.dynaPortAwesomeness)
Protocol=tcp Scope=any IgnoreFailure=yes
Hmm, what does your detect sequence look like in your MBA?
Did you implement
OnDetectUpdateBegin, OnDetectUpdate, OnDetectUpdateComplete?
In OnDetectUpdateBegin are you:
Returning a recommendation of IDOK (not certain of the managed
equivalence of this is)?
In OnDetectUpdate, are
Note, it may be just the ordering of your updates in the feed. I don't think
there is anything preventing you from caching the newest update in your MBA
(after each OnDetectUpdate call, just don't return IDOK which aborts the
looping through the updates), and then in OnDetectUpdateComplete
My mba which has been working in this regard for about a year, is based on
the Wix toolset Setup\WixBA\UpdateViewModel code which implements
DetectUpdateBegin and DetectComplete. Some time ago I added some
customization to these handlers to allow our build process to place builds
into a dev,
Thanks, neslekkim! I am using commandline, and the DirectoryRefId was what
I was missing. Once I fed that into heat (with -dr MyInstallDir), it
started working.
neslekkim wrote
commandline or msbuild?
On commandline you can add -gg to generate guid's when heat is run, or -ag
to use *
Ahh, so you are doing your own downloading of the atom feed. In 3.9, the
engine will download the feed automatically if IDOK is returned from
OnDetectUpdateBegin and there is an Update / element in the BA's manifest.
It is possible that the changes I made to the engine are triggering an
Can someone point me towards some exhaustive information/examples on how to
add upgrade/repair capabilities to my installer? On repair it would
basically just replace the installed files with the ones in the installer
regardless of version, upgrade would naturally only install if the version
in
20 matches
Mail list logo
