Azure SDK 2.7.1 for .NET Extends Capabilities to Visual Studio 2013 -- Visual Studio Magazine

Azure SDK 2.7.1 for .NET Extends Capabilities to Visual Studio 2013

Point release now allows Visual Studio 2013 developers to gain access to Azure management tools, such as Cloud Explorer, HDInsight, and others.

By Michael Domingo
09/02/2015

Developers can get access to Azure through a number of subscription methods: Role Based Access Control, DreamSpark, and Cloud Solution Provider, to name a few. That access is granted through the Azure Software Development Kit 2.7 that was released at the same time as Visual Studio 2015 mid-July. At the time, support was only built in for Visual Studio 2015. This week, a point-point update extends that support to Visual Studio 2013.

Azure SDK for 2.7.1 for .NET sports a number of new tools aimed directly at Visual Studio and .NET developers who want to be able to manage and navigate through the variety of Azure services and access methods without leaving the development environment:

Cloud Explorer: Similar to Solution Explorer, except it allows searching, viewing, property inspection, and diagnosing of Azure resources from within VS.
Azure Resource Manager: Provides native support from within Visual Studio Online for build tasks to create, provision and manage Azure resources.
HDInsight: The cloud analytics and performance monitor adds a number of tooling improvements including expanded IntelliSense support for the Hive Data Manipulation Language, more execution graphing options for drilling into Hive jobs running on the Apache Tez framework, and the addition of a number of templates for Apache Storm and Apache Pig platforms.
Azure AppService Tools: Tools for Web Apps Remote Profiling, API Apps Swagger generation, and multiple account sign-in are now integrated into the Visual Studio environment via Azure App Service. It also uses Azure Resource Management APIs to manage access and authentication. Azure API Apps is also available from within the VS environment, in preview mode, via this tool.
Azure Data Factory: The tool is used for the creation, orchestrtion and management of on-premises and cloud-based data pipelines. ing of on-premises and cloud data sources.

Authentication is also streamlined to resemble single signn-on, now that there's an account picker that allows developers to choose an authentication method that filters access to any needed Azure services throughout a development session. Authentication extends to general Azure subscription methods, as well as those gaining access via DreamSpark, the Cloud Solution Provider program, or Role Based Access Control for those using Visual Studio 2013 with the 2.7.1 update.

About the Author

You Tell 'Em, Readers: If you've read this far, know that Michael Domingo, Visual Studio Magazine Editor in Chief, is here to serve you, dear readers, and wants to get you the information you so richly deserve. What news, content, topics, issues do you want to see covered in Visual Studio Magazine? He's listening at [email protected].

Printable Format

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.