Skip to main content

Posts

Showing posts from May, 2020

Continuous integration workflow template for .NET Core desktop apps with GitHub Actions

We know how time consuming it can be to quickly set up continuous integration and continuous deployment workflows (CI/CD) for your WPF and Windows Forms desktop applications. That’s why, in cooperation with the GitHub Actions team, we have released a starter workflow in GitHub to help you quickly set up and showcase DevOps for your applications using the recently released GitHub Actions . With GitHub Actions, you can quickly and easily automate your software workflows with CI/CD. Integrate code changes directly into GitHub to speed up development cycles Trigger builds to quickly identify build breaks and create testable debug builds Continuously run tests to identify and eliminate bugs Automatically sign, package and deploy branches that pass tests The starter workflow template can be added directly to your project in a few simple steps, and with minimal configuration, allowing you to quic...

Introducing YARP Preview 1

Introducing YARP Preview 1 YARP is a project to create a reverse proxy server. It started when we noticed a pattern of questions from internal teams at Microsoft who were either building a reverse proxy for their service or had been asking about APIs and technology for building one, so we decided to get them all together to work on a common solution, which has become YARP. YARP is a reverse proxy toolkit for building fast proxy servers in .NET using the infrastructure from ASP.NET and .NET. The key differentiator for YARP is that it is being designed to be easily customized and tweaked to match the specific needs of each deployment scenario. YARP plugs into the ASP.NET pipeline for handling incoming requests, and then has its own sub-pipeline for performing the steps to proxy the requests to backend servers. Customers can add additional modules, or replace stock modules as needed. With the basic infrastructure of the proxy now in place, we’ve produced the first official build of YA...

Introducing Project Tye

Project Tye Project Tye is an experimental developer tool that makes developing, testing, and deploying microservices and distributed applications easier. When building an app made up of multiple projects, you often want to run more than one at a time, such as a website that communicates with a backend API or several services all communicating with each other. Today, this can be difficult to setup and not as smooth as it could be, and it’s only the very first step in trying to get started with something like building out a distributed application. Once you have an inner-loop experience there is then a, sometimes steep, learning curve to get your distributed app onto a platform such as Kubernetes. The project has two main goals: Making development of microservices easier by: Running many services with one command Using dependencies in containers Discovering addresses of other services using simple conventions Automating deployment of .NET applications to Kubernetes by: Auto...

F# 5 and F# tools update

We’re excited to announce some updates to F# 5 today! We shipped a lot of preview features since F# 5 preview 1 , and they have all been stabilizing since that release. Today, we’re happy to announce some minor additions to F# 5 and talk about some pretty cool performance work we’ve been doing. Here’s how you get the latest release: Install the latest .NET 5 preview SDK Install Jupyter Notebooks for .NET If you’re using Visual Studio on Windows, you’ll need both the .NET 5 preview SDK and Visual Studio Preview installed . Using F# 5 preview You can use F# 5 preview via the .NET 5 preview SDK , or through the .NET and Jupyter Notebooks support . If you’re using the .NET 5 preview SDK, check out a sample repository showing off some of what you can do with F# 5. You can play with each of the features there instead of starting from scratch. If you’d rather use F# 5 in your own project, you’ll need to add a LangVersion property with preview as the value. It should look somethin...

ML.NET Model Builder is now a part of Visual Studio

ML.NET  is a cross-platform, machine learning framework for .NET developers. Model Builder is the UI tooling in Visual Studio that uses Automated Machine Learning (AutoML) to train and consume custom ML.NET models in your .NET apps. You can use ML.NET and Model Builder to create custom machine learning models without having prior machine learning experience and without leaving the .NET ecosystem. Model Builder in Visual Studio Previously, Model Builder was a Visual Studio extension that had to be installed from the VS Marketplace. Now, Model Builder ships with Visual Studio 16.6 as a preview feature! After enabling the Model Builder feature in VS, all you have to do is right-click on your project in Solution Explorer and add Machine Learning.   New Model Builder Scenario screen Model Builder’s Scenario screen got an update with a new, modern design and with updated scenario names to make it even easier to map your own business problems to the machine learning scenarios o...

ASP.NET Core updates in .NET 5 Preview 4

.NET 5 Preview 4 is now available and is ready for evaluation! .NET 5 will be a current release . Get started To get started with ASP.NET Core in .NET 5.0 Preview4 install the .NET 5.0 SDK . If you’re on Windows using Visual Studio, we recommend installing the latest preview of Visual Studio 2019 16.6 . If you’re on macOS, we recommend installing the latest preview of Visual Studio 2019 for Mac 8.6 . Upgrade an existing project To upgrade an existing ASP.NET Core 5.0 preview3 app to ASP.NET Core 5.0 preview4: Update all Microsoft.AspNetCore.* package references to 5.0.0-preview.4.* . Update all Microsoft.Extensions.* package references to 5.0.0-preview.4.* . See the full list of breaking changes in ASP.NET Core 5.0. That’s it! You should now be all set to use .NET 5 Preview 4. What’s new? Performance Improvements to HTTP/2 By adding support for HPack dynamic compression of HTTP/2 response headers in Kestrel, the 5.0.0-prevew4 release improves the performance of HTTP/2....

.NET Core May 2020 Updates – 2.1.18 and 3.1.4

Today, we are releasing the .NET Core May 2020 Update. These updates contain security and reliability fixes. See the individual release notes for details on updated packages. NOTE: If you are a Visual Studio user, there are MSBuild version requirements so use only the .NET Core SDK supported for each Visual Studio version. Information needed to make this choice will be seen on the download page. If you use other development environments, we recommend using the latest SDK release. .NET Core 3.1.4 and .NET Core SDK ( Download | Release Notes ) .NET Core 2.1.18 and .NET Core SDK ( Download | Release Notes ) Getting the Update The latest .NET Core updates are available on the .NET Core download page . This update will be included in a future update of Visual Studio. See the .NET Core release notes ( 2.1.18 | 3.1.4 ) for details on the release, including issues fixed and affected packages. Docker Images .NET Docker images have been updated for today’s release. The following...

Configuring Azure Services and emulators using Visual Studio

Starting with Visual Studio 16.6 Preview 2 the Connected Services tab offers a new experience called Service Dependencies . You can use it to connect your app to Azure services such as Azure SQL, Storage, Key Vault and many others. Wherever possible local emulation options are also available and more are planned for the future. Add a new Service Dependency You can easily and quickly get the right NuGet packages, start-up code and configuration added to your project for every supported Azure service. You simply click add, pick the service from the list and follow the 2-3 steps in the wizard. Here is an example of adding Azure Cosmos DB Provision a new instance of an Azure service without leaving the IDE In the above example we re-used an existing instance of Azure Cosmos DB, but you can also create new instances of all the supported Azure services without leaving the IDE. Here is Azure Cosmos DB again as an example of provisioning Azure resources from within Visual Studio Config...