Thank you very much. I've just tried your suggestion and it works perfectly for me.
If the you could add an option, in a future version of AI, to configure the firewall as part of a merge module that would be brilliant.
Thank you again.
Paul
Suggested Articles
Search found 4 matches
- Thu Mar 17, 2011 5:13 pm
- Forum: Common Problems
- Topic: Adding Firewall exception for merge modules
- Replies: 4
- Views: 4255
- Jump to post
- Wed Mar 16, 2011 6:43 pm
- Forum: Common Problems
- Topic: Adding Firewall exception for merge modules
- Replies: 4
- Views: 4255
- Jump to post
Re: Adding Firewall exception for merge modules
OK, thanks.
Do you have a recommended method of configuring the firewall exceptions by custom actions, as there seems to be lots of options suggested based on a quick google search?
Do you have a recommended method of configuring the firewall exceptions by custom actions, as there seems to be lots of options suggested based on a quick google search?
- Wed Mar 16, 2011 3:07 pm
- Forum: Common Problems
- Topic: Adding Firewall exception for merge modules
- Replies: 4
- Views: 4255
- Jump to post
Adding Firewall exception for merge modules
Is there any way of configuring the Windows Firewall for items in a merge module?
We have a common core service that we package in our own merge module. I know I can add the firewall exceptions in the main installer, but I can't find a way of adding Program exceptions for the files in the merge ...
We have a common core service that we package in our own merge module. I know I can add the firewall exceptions in the main installer, but I can't find a way of adding Program exceptions for the files in the merge ...
- Wed Feb 09, 2011 1:02 pm
- Forum: Common Problems
- Topic: Signing packages on Win 7
- Replies: 12
- Views: 17516
- Jump to post
Re: Signing packages on Win 7
Hello,
This must be an AI bug, because .NET SignTool.exe is completely unrelated to Capicom.
Actually, CAPICOM is a SignTool.exe requirement. For more information see the Remarks section of this MSDN article .
Regards,
Mihai
Also if you look at the latest version of the SignTool.exe MSDN ...
This must be an AI bug, because .NET SignTool.exe is completely unrelated to Capicom.
Actually, CAPICOM is a SignTool.exe requirement. For more information see the Remarks section of this MSDN article .
Regards,
Mihai
Also if you look at the latest version of the SignTool.exe MSDN ...