News

Microsoft Previews Tye Tool for Microservices Development in VS Code

Microsoft is previewing a new Visual Studio Code extension for working with the open source, experimental Tye project that's used for microservice and distributed application development.

Parked under the .NET Platform repo on GitHub, Tye is a .NET Foundation project designed to ease the development, testing and deployment of microservices and distributed applications. It includes a local orchestrator to make microservices development easier, along with the ability to simplify the deployment of microservices to Kubernetes, the popular container orchestration system.

The GitHub repo says Tye can:

  • Simplify microservices development by making it easy to:
    • Run many services with one command
    • Use dependencies in containers
    • Discover addresses of other services using simple conventions
  • Deploy .NET applications to Kubernetes by:
    • Automatically containerizing .NET applications
    • Generating Kubernetes manifests with minimal knowledge or configuration
    • Using the same conventions as development to keep it consistent

The new Tye extension in the VS Code Marketplace eases the process of running and debugging applications that use Tye from within the popular open source code editor. As the graphic below shows, the week-old tool has been installed 322 times as of this writing.

Tye VS Code Extension
[Click on image for larger view.] Tye VS Code Extension (source: Microsoft).

Specifically, "The VS Code extension makes it easier to initialize, run, view, and manage your Tye application from within VS Code." Microsoft said in a June 1 blog post.

For debugging, developers can debug all services in the project or just a subset. Alternatively, they can run a Tye app without debugging. They can attach the debugger to already running project-based services or to a single service.

Tye Debugging
[Click on image for larger view.] Tye Debugging (source: Microsoft).

"From the explorer, you can view the logs for any of your services, browse to services that have accessible endpoints, and even attach a debugger to any of the .NET services!" Microsoft said. "We have also included a link that lets you quickly navigate to the browser-based Tye dashboard that you may already know and love."

Microservices, of course, are tightly knit with cloud computing, and for many using the VS Code tool, that will mean Microsoft Azure. The Tye GitHub project indicates Tye supports Azure Functions and other cloud functionality.

"This is a continuation of the Tye experiment, where we are learning what the best cloud-native tooling experiences could be," Microsoft said.

About the Author

David Ramel is an editor and writer at Converge 360.

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