SecurityUtilities Class
Provides a set of utility functions for manipulating security permision sets and signing.
MSBuild is now included in Visual Studio instead of the .NET Framework.You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0.
Inheritance Hierarchy
System.Object
Microsoft.Build.Tasks.Deployment.ManifestUtilities.SecurityUtilities
Namespace: Microsoft.Build.Tasks.Deployment.ManifestUtilities
Assembly: Microsoft.Build.Tasks.Core (in Microsoft.Build.Tasks.Core.dll)
Syntax
'Declaration
<ComVisibleAttribute(False)> _
Public NotInheritable Class SecurityUtilities
[ComVisibleAttribute(false)]
public static class SecurityUtilities
[ComVisibleAttribute(false)]
public ref class SecurityUtilities abstract sealed
[<AbstractClass>]
[<Sealed>]
[<ComVisibleAttribute(false)>]
type SecurityUtilities = class end
public final class SecurityUtilities
The SecurityUtilities type exposes the following members.
Methods
Name | Description | |
---|---|---|
ComputeZonePermissionSet | Generates a permission set by computing the zone default permission set, removing any excluded permissions, and adding any included permissions.MSBuild is now included in Visual Studio instead of the .NET Framework.You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
IdentityListToPermissionSet | Converts an array of permission identity strings to a permission set object.MSBuild is now included in Visual Studio instead of the .NET Framework.You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
PermissionSetToIdentityList | Converts a permission set object to an array of permission identity strings.MSBuild is now included in Visual Studio instead of the .NET Framework.You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
SignFile(X509Certificate2, Uri, String) | Signs a ClickOnce manifest or PE file.MSBuild is now included in Visual Studio instead of the .NET Framework.You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
SignFile(String, Uri, String) | Signs a ClickOnce manifest or PE file.MSBuild is now included in Visual Studio instead of the .NET Framework.You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
SignFile(String, SecureString, Uri, String) | Signs a ClickOnce manifest.MSBuild is now included in Visual Studio instead of the .NET Framework.You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
SignFile(String, Uri, String, String) | Signs a ClickOnce manifest or PE file. This overload is new as of Visual Studio 2013 Update 3. This overload allows you to specify the target framework version for the file. You are encouraged to use this overload wherever possible, because the MSBuild process uses SHA256 hashes only when the target framework is .NET 4.5 or higher. If the target framework is .NET 4.0 or below, the SHA256 hash will not be used. MSBuild is now included in Visual Studio instead of the .NET Framework.You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
XmlToPermissionSet | Converts an XML element to a permission set object.MSBuild is now included in Visual Studio instead of the .NET Framework.You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. |
Top
Thread Safety
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.
See Also
Reference
Microsoft.Build.Tasks.Deployment.ManifestUtilities Namespace