Google Cloud Functions Supports .NET Core 3.1 (but not .NET 5) -- Visual Studio Magazine

Google Cloud Functions Supports .NET Core 3.1 (but not .NET 5)

By David Ramel
11/30/2020

Google Cloud Functions -- often used for serverless, event-driven projects -- now supports .NET, but the new support is a release behind Microsoft's latest .NET offering.

On Nov. 19, Google announced support for .NET Core 3.1 in its Function-as-a-Service (FaaS) platform, but that was more than a week after Microsoft shipped the GA version of .NET Core 3.1's successor, .NET 5.

Cloud Functions helps users create single-purpose, stand-alone functions that respond to events such as user interactions or triggers, with the provider taking care of managing servers and runtime environments.

"With Cloud Functions for .NET, now in Preview, you can use .NET Core 3.1 to build business-critical applications and integration layers, and deploy the function in a fully managed environment, complete with access to resources in a private VPC network," Google said. ".NET functions scale automatically based on your load. You can write HTTP functions to respond to HTTP events, and CloudEvent functions to process events sourced from various cloud and Google Cloud services including Pub/Sub, Cloud Storage and Firestore."

**[Click on image for larger view.]** Google Cloud Functions *(source: Google).*

In addition to C#, coders can use F# and Visual Basic to write cloud functions, in conjunction with the Functions Framework for .NET, an open source FaaS framework for creating portable .NET functions. "With Functions Framework you develop and run your functions locally, then deploy them to Cloud Functions, or to another .NET environment," Google said."

That framework includes a template package for use from the command line or Visual Studio, and the templates support VB and F# also.

With the new .NET support for serverless computing, Google Cloud is somewhat catching up to industry leader Amazon Web Services (AWS), which has supported .NET in its AWS Lambda offering for years.

The other "Big 3" cloud provider, Microsoft Azure, naturally supports .NET in its serverless offering, Azure Functions, though .NET Core 3.1 support only arrived in January.

For working with the new .NET Core 3.1 support in Cloud Functions, Google published a .NET Quickstart and pointed to "A Tour of the .NET Functions Framework" written by Jon Skeet.

About the Author

David Ramel is an editor and writer at Converge 360.

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.