Back to Resources

Professional Edition 1.0.5 (January 2021)

Professional Edition 1.0.5 Release Notes

Puma Scan’s 1.0.5 release is an update for the Puma Scan End User, Server, and Azure DevOps Editions.

System Requirements

  • End User Edition for Visual Studio Code requires Visual Studio Code for Windows, macOS, or Linux.

  • End User Edition for Visual Studio requires Visual Studio 2019 v16.0 or higher.

  • End User Edition for Visual Studio 2017 requires Visual Studio 2017 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.

Framework Enhancements

  • Enhancement: Support added for NET Core 3.1+ Entity Framework Raw Sql Query methods.
  • Bug fix: Upgraded to latest version of Microsoft’s MSBuildLocator library in order to support customers with .NET 5 SDK installed. Previously, users may have experienced a WorkloadSdkResolver load failure message.

Server and Azure DevOps Editions

  • Enhancement: New SonarCloud output format to support importing Puma Scan Professional analysis results into By selecting sonarcloud as an output format, a file will be generated using SonarCloud’s Generic Issue Data format. This file can then be included in SonarCloud’s analysis via SonarCloud’s platform dependent external report paths property. For example, in Azure DevOps, the external report path is specified via the sonar.externalIssuesReportPaths property in SonarCloud’s Prepare Analysis on Sonar Cloud task.

End User Edition for Visual Studio Code

  • Bug fix: Puma Scan Analysis failure occurs when scanning projects in which the parent folder contains a period.
  • Bug fix: Projects with Project references not loaded into the workspace causes an Puma Scan Analysis failure.
  • Bug fix: Puma Scan is not detecting when a workspace or project folder is not open. Thus will attempt to scan any and all projects located on the file system and cause a starvation of resources.