WindowsFirewallHelper Versions Save

Added .net5 as a release target

https://www.nuget.org/packages/WindowsFirewallHelper/2.2.0.86

• Fixed a problem with NetworkAddress start and end addresses (#46)
• Allows remote domain machines control (#42)
• Allows COM object recreation (#34)
• First release out of beta

https://www.nuget.org/packages/WindowsFirewallHelper/2.1.4.81

This is a maintenance release focusing on an issue about inclusive port ranges as discoursed in #36

https://www.nuget.org/packages/WindowsFirewallHelper/1.6.3.46

• System.ServiceProcess.ServiceController package updated to v4.7
• It is now possible to create an instance of FirewallWASRuleGroup simply by providing the name of the group
• Collections now have indexer for faster access to a specific item as well as a remove method

https://www.nuget.org/packages/WindowsFirewallHelper/2.0.4.70-beta2

• Fixed multiple bugs and problems
• New methods added
• Minor changes in the API

https://www.nuget.org/packages/WindowsFirewallHelper/2.0.2.29-beta1

• Parse method added to all types of addresses
• FirewallV1 renamed to FirewallLegacy and FirewallV2 renamed to FirewallWAS along with other naming changes
• SingleIP now correctly parses IPRanges and NetworkAddresses containing only one IPAddress
• Moved hardcoded ProgIds from all classes to the COMInterop interfaces
• FirewallProtocol.Any is again considered a valid value for FirewallWAS
• IFirewall.Profiles is now read-only
• Fixed a problem with FirewallLegacy still trying to resolve rule names even when the Name property is used
• Method for FirewallProduct registration and information moved to FirewallManager
• FirewallWASRuleWin7 and FirewallWASRuleWin8 now has a public general constructor
• IFirewallRule.Profiles no longer has a setter
• Default Protocol changed from Any to TCP in FirewallLegacy for better compatibility with newer versions of Windows Firewall
• Fixed a bug that made it impossible to create rules for FirewallLegacy
• Port range is now inclusive
• Assembly is now signed
• XML documentation file is now a part of NuGet package

https://www.nuget.org/packages/WindowsFirewallHelper/2.0.1.11-alpha3

• Port Range is now inclusive
• Assembly is now signed
• XML documentation file is now a part of NuGet package

https://www.nuget.org/packages/WindowsFirewallHelper/1.6.3.40

THIS IS A PRE-RELEASE. DON'T USE IT UNLESS YOU HAVE ONE OR MORE PROBLEMS WITH V1

• Rules collection is no longer cached and should be real-time
• Allows accessing from multiple threads with STA [Not-Testet]
• Fixed multiple major and minor bugs (more details are available in the description of commits)
• Third party firewall support for extending library's functionalities removed
• New FirewallProduct class added to get information about the current active firewall software
• Windows XP implementation should be much more stable now [Not-Testet]
• A new method added to detect if the Firewall service is in fact running
• A new method added to reset Windows Firewall settings to default
• A new property added to detect if the Firewall settings are effective or if they are controlled by GP
• Minor changes to the sample project to make it more usable

https://www.nuget.org/packages/WindowsFirewallHelper/2.0.0.3-alpha

• Fixed a bug with SingleIP when stored inside a hashtable
• Fixed a bug with one of Firewall v2 CreatePortRule() overloads not working
• Fixed a bug with LocalPorts and RemotePorts properties failing to save settings when multiple ports are present

https://www.nuget.org/packages/WindowsFirewallHelper/1.6.2.35

• First NetStandard2 release compatible with NetCore2+ #13

https://www.nuget.org/packages/WindowsFirewallHelper/1.6.0.33