ServiceStack based web service and client tools for performing remote Authenticode and .NET Assembly Strong Name signing
Features include:
- .NET strong naming and Authenticode signing in a single web service call.
- Uses Azure Storage for robust transfer of files.
- Authenticode signs all files types that CryptoAPI can sign, including .Exe, .Dll, Powershell scripts, .Msi and OPC formats, such as .VSIX, .NuPkg, .Xps and Office files.
- Cmdlets for signing files and administering the service
- MSBuild tasks and targets for integrating signing into your build process
###Requirements for usage
- Powershell 3.0
- Included with Windows 8, for Windows 7 64-bit or 32-bit
###Development Requirements
- Visual Studio 2012 (Visual Studio 2010 SP1 will probably work)
- Wix 3.7
- Azure Storage Emulator
- Plus all the usage requirements above
###Folder Structure
- ClientLib
- A library of code used by clients of the SigningApi. The common code between the Cmdlets and the MSBuildTasks
- Cmdlets
- Powershell Cmdlets for initializing, maintaining the service and signing files.
- CmdletTesting
- A few basic unit tests for the Cmdlets. Not very well maintained.
- DTO
- The request and response objects for the service used by ServiceStack. Also includes some wrapping of Azure Blob Service to make it more testable
- Installer
- Wix project for installing the Cmdlets
- MSBuildTasks
- MSBuild tasks and targets for signing files as part of the build process
- MSBuildTest
- Unit tests for the MSBuildTasks. Not well maintained.
- SigningApi
- ServiceStack based web service running the signing tool
- includes
- Files that ware used as part of the build process. Includes the version files
- tools
- Tasks and targets used as part of the build process that are "external." Someday, these will come via NuGet packages