From 0f2fb968a2afdd9e950727250a8069f37bd3d2fc Mon Sep 17 00:00:00 2001 From: Sean Hall Date: Fri, 4 Dec 2020 17:23:52 -0600 Subject: xsd got moved to doc repo. Update dependencies. --- global.json | 2 +- src/ca/fwca.vcxproj | 8 +- src/ca/packages.config | 4 +- src/wixext/WixToolset.Firewall.wixext.csproj | 5 +- src/wixext/firewall.xsd | 217 --------------------------- src/wixlib/firewall.wixproj | 2 +- 6 files changed, 10 insertions(+), 228 deletions(-) delete mode 100644 src/wixext/firewall.xsd diff --git a/global.json b/global.json index 10345833..77a81322 100644 --- a/global.json +++ b/global.json @@ -1,5 +1,5 @@ { "msbuild-sdks": { - "WixToolset.Sdk": "4.0.0-build-0163" + "WixToolset.Sdk": "4.0.0-build-0170" } } diff --git a/src/ca/fwca.vcxproj b/src/ca/fwca.vcxproj index 6e392b8f..5e9a1db6 100644 --- a/src/ca/fwca.vcxproj +++ b/src/ca/fwca.vcxproj @@ -2,8 +2,8 @@ - - + + @@ -75,7 +75,7 @@ This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is {0}. - - + + diff --git a/src/ca/packages.config b/src/ca/packages.config index e3dc0e43..9d88f529 100644 --- a/src/ca/packages.config +++ b/src/ca/packages.config @@ -1,5 +1,5 @@  - - + + \ No newline at end of file diff --git a/src/wixext/WixToolset.Firewall.wixext.csproj b/src/wixext/WixToolset.Firewall.wixext.csproj index 07d5de56..6704dad2 100644 --- a/src/wixext/WixToolset.Firewall.wixext.csproj +++ b/src/wixext/WixToolset.Firewall.wixext.csproj @@ -1,4 +1,4 @@ - + @@ -13,7 +13,6 @@ - @@ -27,6 +26,6 @@ - + diff --git a/src/wixext/firewall.xsd b/src/wixext/firewall.xsd deleted file mode 100644 index 20ad065f..00000000 --- a/src/wixext/firewall.xsd +++ /dev/null @@ -1,217 +0,0 @@ - - - - - - - - The source code schema for the WiX Toolset Firewall Extension. - - - - - - - - - Registers an exception for a program or a specific port and protocol in the Windows Firewall - on Windows XP SP2, Windows Server 2003 SP1, and later. For more information about the Windows - Firewall, see - About Windows Firewall API. - - - - - - - - - - - - Explicitly-listed remote addresses that this exception allows through the - firewall. - - - - - - - - - Unique ID of this firewall exception. - - - - - - - - Name of this firewall exception, visible to the user in the firewall - control panel. - - - - - - - - The scope of this firewall exception, which indicates whether incoming - connections can come from any computer including those on the Internet - or only those on the local network subnet. To more precisely specify - allowed remote address, specify a custom scope using RemoteAddress - child elements. - - - - - - - - - - - - - - Port to allow through the firewall for this exception. - - If you use Port and also File or Program in the same - FirewallException element, the exception will fail to install on - Windows XP and Windows Server 2003. IgnoreFailure="yes" can be used to - ignore the resulting failure, but the exception will not be added. - - - - - - - - IP protocol used for this firewall exception. If Port is defined, - "tcp" is assumed if the protocol is not specified. - - If you use Protocol and also File or Program in the same - FirewallException element, the exception will fail to install on - Windows XP and Windows Server 2003. IgnoreFailure="yes" can be used to - ignore the resulting failure, but the exception will not be added. - - - - - - - - - - - - - - Identifier of a file to be granted access to all incoming ports and - protocols. If you use File, you cannot also use Program. - - If you use File and also Port or Protocol in the same - FirewallException element, the exception will fail to install on - Windows XP and Windows Server 2003. IgnoreFailure="yes" can be used to - ignore the resulting failure, but the exception will not be added. - - - - - - - - Path to a target program to be granted access to all incoming ports and - protocols. Note that this is a formatted field, so you can use [#fileId] - syntax to refer to a file being installed. If you use Program, you cannot - also use File. - - If you use Program and also Port or Protocol in the same - FirewallException element, the exception will fail to install on - Windows XP and Windows Server 2003. IgnoreFailure="yes" can be used to - ignore the resulting failure, but the exception will not be added. - - - - - - - - If "yes", failures to register this firewall exception will be silently - ignored. If "no" (the default), failures will cause rollback. - - - - - - - - Profile type for this firewall exception. Default is "all". - - - - - - - - - - - - - - - Description for this firewall rule displayed in Windows Firewall manager in - Windows Vista and later. - - - - - - - - If "yes", registers an outbound firewall rule. - - - - - - - - - - A remote address to which the port or program can listen. Address formats vary - based on the version of Windows and Windows Firewall the program is being installed - on. For Windows XP SP2 and Windows Server 2003 SP1, see - - RemoteAddresses Property. - For Windows Vista and Windows Server 2008, see - - RemoteAddresses Property. - - - - - - - A remote address. - - - - - - - - - Values of this type will either be "yes" or "no". - - - - - - - diff --git a/src/wixlib/firewall.wixproj b/src/wixlib/firewall.wixproj index 049b26b1..242fa56e 100644 --- a/src/wixlib/firewall.wixproj +++ b/src/wixlib/firewall.wixproj @@ -20,7 +20,7 @@ - + -- cgit v1.2.3-55-g6feb