Blog

Today I’ll show a simple example of how to create a .Net Core Health Endpoint Monitoring Middleware. If you need to know about the Health Endpoint Monitoring Pattern check: https://msdn.microsoft.com/en-us/library/dn589789.aspx Create the application # Open a command prompt and run

Shadow IT, defined as the use of IT systems, solutions and services inside organizations without explicit organizational approval, has always been seen as a problem and a huge risk for the enterprise. But what if I tell you that you should learn from Shadow IT and use it on your advantage instead of fighting it and suppressing it?

For ages I’ve been using T4 templates as main tool for code generation and scaffolding, but now that I’m an absolute fan of Visual Studio Code and .Net Core I need to explore other options such as Yeoman, Scripty and Roslyn. This post is just the result of my first and simplest experiment with .Net Core, Roslyn and Code Generation.

Last Thursday I attended a Meetup hosted by my friends of @MsCodersMadrid in Madrid where, thanks to @snavarropino, I learned a bit about the NancyFX open source framework. I really couldn’t believe my eyes when I saw how simple it is to use NancyFX to write a Web API. Two of the things that got my attention were: the out of the box content negotiation and zero configuration dependency injection.

I’ve been watching Black Mirror, a Netflix Original Series with a profound message which makes the spectator think and really reflect on how technology and social networks are transforming our lives through a series of non-related episodes. In one of the episodes, people live in a world where the more social influence they have (i.e. number of Facebook likes, followers or likes in Twitter, etc.) the more they can achieve or buy.

Last Thursday I started reading the Free eBook: “Containerized Docker Application Lifecycle with Microsoft Tools and Platform” by Cesar de la Torre. The book is really easy to read and really gives the reader a glimpse on the way to approach the overall application lifecycle when using containers and Microsoft Technologies. One of the interesting things he mentions is the ability to debug your source code inside a container using Visual Studio or Visual Studio Code, so I decided to try it out and Debug ASP.NET Core on Docker with Visual Studio Code

On November 16th, Microsoft announced the .NET Core Tools MSBuild"alpha". I’ve been developing .Net Core applications with Visual Studio Code for a while now, and I needed to try the new tooling. In this post I’ll show you which were my First steps with .NET Core Tools MSBuild “alpha” Installing .NET Core SDK 1.0 Preview 3 build 004056 # The first step was to install the new tools from: .NET Core SDK 1.0 Preview 3 build 004056

This week I decided to modify the sample of my previous post: Step by step: Scale ASP.NET Core with Docker Swarm so you can add TLS to your ASP.NET Core applications and Dockerize it. Let’s see how I changed the application in order to make it work: Add HTTPS support for Kestrel # I added the following line to the dependencies in the project.json file.

A few weeks ago I posted Step by step: ASP.NET Core on Docker were I showed how to build and run a Docker image with an ASP.NET Core application. Today I bring you: Step by step: Scale ASP.NET Core with Docker Swarm so you can scale out or in the same application. Assuming you have Docker 1.12 or later installed and running, follow this steps:

If you intend to use the WindowsAzure.Storage library with .Net Core you’ll hit a"compatibility wall" trying to make it work. So how can we use .Net Core to Create Azure Blob Storage SAS Keys? Add the System.Security.Cryptography.Algorithms dependency # Add the following dependency in your project.json file

I started the day in a coffee shop. I got a nice spot with a window right next to me. As I take out my Surface Book and turn it on, in a matter of seconds my face is recognized so I don’t have to use the keyboard to login. A couple of minutes later Cortana reminds me that

Las week we discovered that some of our test would"randomly" fail depending of the time of the day. After investigating the issue we found that the culprit was that the service being tested was taking decisions based on the current system time (DateTime.Now) leading to different outcomes through the day. So how do we deal with time dependencies in tests?

This week I cleared the 70-533 Implementing Microsoft Azure Infrastructure Solutions exam, and I want to share with you tips about the exam and the resources I used to study: Should you take the exam? If you are an Infrastructure Geek, Developer or Software Architect looking to validate your Microsoft Azure skills then this exam is for you. Also note that Microsoft expects you to:

This week I have to give an introductory talk on DevOps and Docker and therefore I decided to prepare a simple Step by step: ASP.NET Core on Docker sample. Assuming you have Docker installed and running, follow these 4 simple steps: Create a dockerfile # On your Docker box create a dockerfile with the following contents

NOTE: This post is out of date. Please read: Updated Step by step: Serilog with ASP.NET Core for an update. # Last week I wrote about .NET Core and Microsoft Bot Framework and I’m still learning and playing with it. The thing is that once I implemented more features and deployed the bot to Azure it didn’t work. So I had to find a way to log and trace what was happening in order to diagnose and fix the problem.

Today I’ll show you how to create a simple Skype bot that will reply with the same text message you send to it. You’ll be using .Net Core and Microsoft Bot Framework. As you already know not every library has been ported to .Net Core so you’ll have to use the Microsoft Bot Connector API – v3.0 to bring the bot to life.

Today I’ll show you how to develop a Web API to Create vCard QR Codes using Azure Functions. But wait what are Azure Functions? As defined by Microsoft: Azure Functions is a serverless event driven experience that extends the existing Azure App Service platform. These nano-services can scale based on demand and you pay only for the resources you consume.

We know that cloud computing is “the new normal” just like virtualization was in the past. And we also know that the adoption of cloud computing by your organization can come with a series of benefits including: Reduced IT costs: You can reduce both CAPEX and OPEX when moving to the cloud. Scalability: In this fast changing world it is important to be able to scale up or down your solutions depending on the situation and your needs without having to purchase or install hardware or upgrades all by yourself. Business continuity: when you store data in the cloud, you ensure it is backed-up and protected which in turn helps with your continuity plan cause in the event of a crisis you’ll be able to minimize any downtime and loss of productivity. Collaboration: Cloud services allow you share files and communicate with employees and third-parties in this highly globalized world and in a timely manner. Flexibility: Cloud computing allows employees to be more flexible in their work practices cause it’s simpler to access data from home or virtually any place with an internet connection. Automatic updates: When consuming SaaS you’ll be using the latest version of the product avoiding the pain and expensive costs associated with software or hardware upgrades. But once you ask yourself: what can possibly go wrong? You open your eyes to a “cloudy weather” where you must plan, identify, analyze, manage and control the risks associated with moving your data and operations to the cloud. To help you with the identification process, here is a list of risks that your organization can face once you start or continue the transition to the cloud:

Today I’ll show you how to create a small console application that will Detect and Blur Faces with .NET Core and Face API. First be aware of the following prerequisites: **OS** **Prerequisites** Windows Windows: You must have .NET Core SDK for Windows or both Visual Studio 2015 Update 3* and .NET Core 1.0 for Visual Studio installed. linux, mac or docker checkout .NET Core You will also need an Azure Cognitive Services Face API account and the correct set of access keys. (Start here: Subscribe in seconds if you need a Cognitive Service Account and here for the Documentation)

Today I’ll show you how to create a small console application with a Step by step: Entity Framework Core and Shadow Properties example. We’ll be modifying the code from my previous post: Step by step: .NET Core and Entity Framework Core to make the Student entity auditable without creating public/protected properties or private fields to hold the typical audit info (CreatedBy, CreatedAt, UpdatedBy and UpdatedAt) database fields.