Microsoft.VisualStudio.Azure.CodeAnalysis
If you’re creating Azure cloud applications with a high scalability target in Visual Studio, you’ll find the Azure Code Analysis package very helpful. While you’re coding and leveraging new Visual Studio 2015 capabilities, the Code Analyzer suggests optimal coding practices and workflow improvements. It notifies you if it detects patterns in your code that will degrade app performance, compromise security, provide inconsistent results, or use deprecated APIs or techniques. The following rules are included in this package: - Avoid using default (in-process) session state mode - Run method should not be async - Use Service Bus Shared Access Signature authentication - Consider using OnMessage method to avoid "receive loop" - Consider using asynchronous Service Bus methods - Consider partitioning Service Bus queues and topics - Do not set SharedAccessStartTime - Shared Access Policy expiry time must be more than five minutes - Use CloudConfigurationManager - Avoid using hard-coded connection strings - Use diagnostics configuration file - Avoid declaring DbContext objects as static For more information about the code analysis rules – http://go.microsoft.com/fwlink/?LinkId=403658
Install
dotnet add package Microsoft.VisualStudio.Azure.CodeAnalysis --version 0.2.0-beta
Install-Package Microsoft.VisualStudio.Azure.CodeAnalysis -Version 0.2.0-beta
<PackageReference Include="Microsoft.VisualStudio.Azure.CodeAnalysis" Version="0.2.0-beta" />
Frameworks
No framework metadata available.
Dependencies
No declared dependencies.
Adoption guide
A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.
This version is marked prerelease. Validate its API and upgrade path before production use.
No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.
No target framework metadata is available. Confirm compatibility in a representative project before standardising on this package.
How to read this guidance
Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.
Useful next steps
Move from package metadata to a concrete selection or review workflow.