release-notes
Puma Scan’s 1.0.1 release is an update for the Puma Scan End User, Server, and Azure DevOps Editions.
End User Edition requires Visual Studio v15.9 or higher.
Server Edition requires a Windows Server with the following:
.NET Framework v4.7.2
The Build Tools for Visual Studio 2017 and 2019 are both supported. Ensure you have at least 1 of the following installed:
Build Tools 2017 version 15.8 or higher
Build Tools 2019 version 16.4 or higher
Azure DevOps Edition requires a hosted Azure Build Pipeline using the vs2017-win2016 or windows-2019 build agent.
AuthorizationFilterAttribute
in the System.Web.Http.Filters
namespace is not correctly recognized by the Puma Scan engine.Critical patch: Azure hosted windows-2019
build agents are being migrated to image version 20200820.1, which uses the latest version of MSBuild (>=16.7). MSBuild (>=16.7) causes the following exception when running the build task:
Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime.CompilerServices.Unsafe, Version=4.0.4.1, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
Azure DevOps users will need to update their build pipeline definitions from Puma Scan build task 0.* to 1.* to correct this issue.
Critical patch: The latest versions of MSBuild (>=16.7) throws the following exception for Puma Scan Server Editions < 1.0.
Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime.CompilerServices.Unsafe, Version=4.0.4.1, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
Server Edition users will need to upgrade to Puma Scan Server Edition > 1.0 to correct this issue.
Enhancement: License details are now included when executing Puma Scan with the --system-identification
switch.