Open Source 'Infrastructure-as-Code' SDK Adds .NET Core Support for Working with Azure -- Visual Studio Magazine

Open Source 'Infrastructure-as-Code' SDK Adds .NET Core Support for Working with Azure

By David Ramel
11/12/2019

Pulumi, known for its "Infrastructure-as-Code" cloud development tooling, has added support for .NET Core, letting .NET-centric developers use C#, F# and VB.NET to create, deploy, and manage Azure infrastructure.

The Pulumi SDK, available on GitHub, already supported the JavaScript, TypeScript, Python, and Go programming languages.

Now, .NET developers can use their favorite languages to work with the full gamut of Azure infrastructure, including Kubernetes, Functions, AppService, Virtual Machines, CosmosDB, and so on.

That's done with the open source SDK and assorted libraries, which can be wrangled with an included command-line interface (CLI) tool. In a guest post on the Microsoft development blog site, the company said the benefits of adding .NET Core support include allowing .NET coders to:

Automatically create, update, or delete cloud resources using Pulumi's infrastructure as code engine, removing manual point-and-clicking in the Azure UI and ad-hoc scripts.
Use their favorite IDEs and tools, including Visual Studio and Visual Studio Code, taking advantage of features like auto-completion, refactoring, and interactive documentation.
Catch mistakes early on with standard compiler errors, Roslyn analyzers, and an infrastructure-specific policy engine for enforcing security, compliance, and best practices.
Reuse any existing NuGet library, or distribute their own, whether that's for infrastructure best practices, productivity, or just general programming patterns.
Deploy continuously, predictably, and reliably using Azure DevOps Pipelines, GitHub Actions, or one of over a dozen integrations.
Build scalable cloud applications using classic infrastructure cloud native technologies like Kubernetes, Docker containers, serverless functions, and highly scalable databases such as CosmosDB into their core development experience, bringing them closer to application code.

Read the post for more details, including an example global database with serverless app.

About the Author

David Ramel is an editor and writer at Converge 360.

Printable Format

comments powered by Disqus

Featured

Copilot AI Billing Shock Met with Meters, Caps and Token-Saving Tools

GitHub is layering spending limits, expanded credit allowances and increasingly granular usage reporting onto Copilot, while Microsoft is reworking Visual Studio and VS Code to expose -- and reduce -- the cost of agentic development.
The AI-Powered Software Development Lifecycle

René van Osnabrugge makes the case that AI's biggest opportunity in software development is not faster coding -- it's reducing the friction everywhere else in the SDLC.
Copilot Usage-Based Billing Gets a Token Dashboard

Microsoft is keeping Visual Studio's new built-in Agent Skills switched off by default while a public dashboard measures whether their performance gains justify the additional tokens they may consume.
VS Code 1.129 Introduces Agent Host and Experimental Agents Window Editor

Visual Studio Code 1.129 adds a dedicated process for running AI agent sessions and an experimental docked editor for reviewing agent-generated changes.