Re: [WiX-users] Multiple Firewall Exceptions with the same name

2014-09-02 Thread ferdi.oeztuerk 
Hi

First thing, during setup authoring you should not use fire&forget behavior. So 
I would recommend not to use IgnoreFailure="yes" until you're very sure your 
code is rock-solid.
If there's no obvious error during installation time you can still try to 
refactor your code.

I guess FirewallException takes Name field of parent File element to iterate 
through. So in your case it's always DsNetConfig.exe. What you could try is 
leave out the Name and let WiX define it.

Next possibly working solution: In my setups I always use Port exceptions 
instead of Program exceptions.
For that case I would recommend making components for each FirewallException 
(for each port) and controlling it by the component states of the programs 
which need the regarding ports.

Regards
Ferdi

-Original Message-
From: Marko Kaiser [mailto:mkai...@dspace.de]
Sent: Freitag, 4. Juli 2014 12:06
To: 'wix-users@lists.sourceforge.net'
Subject: [WiX-users] Multiple Firewall Exceptions with the same name

Hi,

I'm facing a problem with firewall exceptions. I create wxs-Files which contain 
the same file at 2 or 3 different directories.
Those files have a child element for creating a firewall exception. The name of 
the firewall exception is always the same.
This leads to the fact, that in case of installation only the last exception 
with the common name is visible in the Windows Firewall rule overview.



  

  




  

  



My questions is: Do I need to rename all firewall exception name "text" to 
something unique like "text1", "text2" ?

Kind regards,
Marko Kaiser

--
Open source business process management suite built on Java and Eclipse Turn 
processes into business applications with Bonita BPM Community Edition Quickly 
connect people, data, and systems into organized workflows Winner of BOSSIE, 
CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise private information. If you have received it in 
error, please notify the sender immediately and delete the original. Any other 
use of the email by you is prohibited.

--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Multiple Firewall Exceptions with the same name

2014-07-04 Thread Phill Hogland 
The Windows Advanced Firewall expects, what the WixFirewallExtension calls
FirewallException/@Name, to be a unique string for each rule, otherwise
multiple MSI entries for the same firewall rule.  I tend to use preprocessor
strings that equate to 'CompanyName AppName' so that they are grouped
together with the company name and the string describes the particular
application which needs the exception.  (It would be nice to be able to set
the WAF Group attribute, but I have not worked on a solution to that issue
yet.)



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Multiple-Firewall-Exceptions-with-the-same-name-tp7595651p7595654.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Multiple Firewall Exceptions with the same name

2014-07-04 Thread Marko Kaiser 
Hi,

I'm facing a problem with firewall exceptions. I create wxs-Files which contain 
the same file at 2 or 3 different directories.
Those files have a child element for creating a firewall exception. The name of 
the firewall exception is always the same.
This leads to the fact, that in case of installation only the last exception 
with the common name is visible in the Windows Firewall rule overview.



  

  




  

  



My questions is: Do I need to rename all firewall exception name "text" to 
something unique like "text1", "text2" ?

Kind regards,
Marko Kaiser

--
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users