Hello, I'm   Jason

At TechBash 2018, Microsoft’s Paul Yuknewicz talked about five Azure services every developer should know. Watch the talk on the TechBash YouTube video to know more.

If you’re using a custom package manage, such as JFrog, Verdaccio, or Azure Artifacts, you’ll notice that each includes an upstream feed allowing you to cache publicly available npmjs.org packages. However, you may prefer to use the public feed for public packages assuring that you have the latest versions. In this case, you’ll want to scope your NPM repository. In a lot of cases, you’ll have a username and password accompanying the custom NPM feed. So, I recommend referencing the repository in an .npmrc within the project and storing your credentials in an .npmrc file in your default user bin (in Windows, this is usually %userprofile%)

In an earlier post, I blogged about using an Azure Logic App to distribute a link to an RSS feed item. One of the actions I had identified was to send a tweet to followers of mine.  However, late on Friday I had tweaked my Logic App to show more information. As a result, I started running into errors in my Logic App like the following:

Yesterday I shared a post about a free eBook titled Architecting Modern Web Application with ASP.NET Core and Microsoft Azure. Within that book, there were samples shared about a monolithic online store. This particular book, authored by Cesar de la Torre from Microsoft, takes that same example and explains how to containerize the application. The book titled .NET Microservices – Architecture for Containerized .NET Applications provides best practices using .NET Core and Docker. It explains how microservices communicate between one another and how to migrate legacy applications to a microservice-based architecture. You can obtain a copy of this eBook here.

Steve Smith, also known as Ardalis, has recently released a free eBook titled Architecting Modern Web Applications with ASP.NET Core and Microsoft Azure. You can obtain this free eBook here. The book reviews an online store application sample that demonstrates some of the principles and patterns described in the book. The book follows a monolithic architecture approach, but there is an accompanying book, that I blogged about here, that discusses microservice-based architecture using the same online store sample.

The acquisition of GitHub by Microsoft was completed less than 24 hours ago. Nat Friedman posted about the acquisition becoming final and emphasized that not only will GitHub remain a separate company, it will continue to invest in many of the projects it believes in. Congratulations to both GitHub and Microsoft. It will be interesting to see what the future holds and how the DevOps process will continue to evolve. I’m already excited to see some of the “paper cuts” that the GitHub team has already solved.

Azure DevOps is currently undergoing a facelift. If you are using the new design and you leverage the Package Management (Artifacts) option in Azure DevOps:

It’s possible that you need your application to handle the datetime values being sent to your app service. One reason for this is that date and time values being passed in may not include the proper time zone designation. By default, Azure Web Apps use UTC settings. To change this value, visit your Azure App Service. In the App Service menu, scroll to Application settings. Add a new setting under Application Settings called WEBSITE_TIME_ZONE.

At TechBash earlier this month, Jeremy Likness shared an in-depth overview of NoSQL. He talked about Azure CosmosDB and different types of NoSQL data structures. Jeremy blogged about it placing the full deck of his presentation on his site at https://blog.jeremylikness.com/say-yes-to-nosql-for-net-sql-developers-74391f785133.

Imagine that you’ve published a web app to an app service in Azure. You’ve tested the app and then head out to dinner with family and friends. You decide to showcase your website over dinner and see an error. Now what?