News

Cloud Foundry Now Supports .NET, Azure Natively

Pivotal's Cloud Foundry 1.6 platform allows .NET apps to run on Pivotal's cloud, as well as on a number of ALM toolchain products.

Pivotal Software Inc. has released a new version of its Cloud Foundry (PCF) platform with expanded support for .NET applications, as well as Microsoft Azure and several ALM toolchain products.

The native support for .NET applications means apps can now run on the PCF 1.6 platform and allows early access support for Microsoft's Azure cloud. ".NET is the No. 2 enterprise language, and we have a lot of customers who are dying to use it with Cloud Foundry," said James Watters, vice president of Product, Marketing and Ecosystems in Pivotal's Cloud Foundry group. "This is the first enterprise-grade platform for cloud native apps to add .NET support."

PCF 1.6 also underscores Pivotal's ongoing partnering strategy with new relationships with GitLab, CloudBees and JFrog. Customers can use Pivotal's Tracker project management tool to integrate platform-managed versions of the GitLab source code repository, the Jenkins for continuous integration/continuous delivery server and the Artifactory binary repository manager.

GitLab is coming to the platform natively. "The cool thing about GitLab is they're like GitHub Enterprise, but open source," Watters said. "So, as we need features in the platform, we can contribute them."

"Enterprise companies are seeking control of their development tool chain as a source of competitive advantage," said Sytse Sijbrandij, GitLab co-founder and CEO, in a statement. "It is more flexible, more integrated, and more secure. The Pivotal and GitLab collaboration is a natural outcome of this larger trend, and we are thrilled to be the source control repository of choice for application development on Pivotal Cloud Foundry."

Pivotal's commercial version of the open source Cloud Foundry, launched in 2013, comes with a self-healing application runtime, support for open source programming languages and frameworks, deployment tools, centralized logging, health monitoring and an application services framework.

According to the Cloud Native Computing Foundation, the increasingly used term "cloud native" refers to application development that involves systems that are container packaged, dynamically managed and microservices-oriented.

About the Author

John K. Waters is the editor in chief of a number of Converge360.com sites, with a focus on high-end development, AI and future tech. He's been writing about cutting-edge technologies and culture of Silicon Valley for more than two decades, and he's written more than a dozen books. He also co-scripted the documentary film Silicon Valley: A 100 Year Renaissance, which aired on PBS.  He can be reached at [email protected].

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.

Subscribe on YouTube