ASP.NET Core is a cross-platform, open-source framework for building modern , cloud-based, connected applications. With ASP.NET core you can build web apps, API APS, Microservices, Mobile backends, and IoT apps.
In part 1 of this blog post series, I talked about one of the most critical “technologies” that people leverage to create microservices, and that is containers. In this post we will discover, the most used product to create and run containers and that is Docker.
In this first post in a 7-part series, Premier Consultant Ilias Jennane explains the fundamentals of containers and Docker.
Using Azure services like AKS, Azure Container Instances and Azure Dev Spaces makes setting up a cluster and testing your containers relatively simple.
In this walkthrough, our App Dev Managers show how to install, configure and containerize a simple webapp to help you get up and running with Docker.
JetPack 4.2 includes an Ubuntu 18.04 environment and updates to CUDA, Tensorflow, and Open CV. One of the best changes is support for Python 3 in the version of Open CV provided. In JetPack 3.3 a build of Open CV was necessary to support Python 3, and this was not a trivial undertaking.
Visual Studio Code offers feature parity with Visual Studio 2017/2019 when it comes to developing a containerized Asp.Net Core application. Since VSCode is cross platform, you can develop your next container DotNetCore application on a Linux or Mac while having access to all the great features that Windows users enjoy on VS2017/2019.
Running Linux containers on a Windows host has been available for awhile now. However, getting Windows and Linux containers to communicate without Docker Compose results in using the containers’ IP Addresses. This is not a good solution since container IP Addresses change often.
App Dev Managers Anand Shukla and Sash Kavalaparambil provide step by step instruction to run a .NET Core Web Application in Docker container using Docker Desktop for Windows.
Enterprise organizations today have numerous simple CRUD based applications that call for modernization without necessarily needing to re-architect the legacy apps. If you have an existing .NET app that could use CI/CD but not necessarily any immediate rearchitecting efforts, this blog is for you.