Findings and thingies

Looking for great input on .NET architecture? Then have a look at this tweet by Nish Anil. Microsoft made four new e-books available. These are in detail:

• Architecting Cloud-Native .NET Apps for Azure
• Blazor for ASP.NET Web Forms Developers
• gRPC for WCF developers e-book
• Modernizing Desktop Apps on Windows 10 with .NET Core 3.0

Are you an ASP.NET developer who is interested in Kubernetes? Have a look at this introduction: »ASP.NET Community Standup - Feb 25, 2020 - Intro to Kubernetes for ASP.NET Core devs«

If you are using Git you've probably heard of Git Flow. George Stocker has an interesting point in »Please stop recommending Git Flow!«.

Talking about monitoring or observability? Have a look at »Observability is a Many-Splendored Definition«. You should no longer be talking about monitoring but instead about observability.

Trying to understand how you need to do authentication using Power Platform's CDS? Then have a look at »How to authenticate your code with Azure Active Directory and Common Data Service« by Jens Christian Schrøder.

»How to merge two or multiple git repositories into one« was a huge time saver for me last week because I needed to merge two different Git repositories. As I had done this never before this article was a big time saver for me.

Dona Sarkar who is a always recommendation to follow on twitter, if you are interested in #PowerPlatform, tweeted about a great demo by Chris Huntingford. He demoes end to end how to built a complete application using #PowerPlatform in 45 minutes.

Matthew Devaney tweeted some highlights from Michał Guzowski.

1. 10 tips I wish to know before I’ve started with PowerApps
2. How to overcome 500 items limit in PowerApps
3. PowerApps components patterns

But in general you should keep an eye on the blog of Michał if you are interested in Power Platform/Apps topics.

Microsoft lately publishes more and more documents which in the past you would only have access to if you attended a training. Manuela tweeted about the materials for the 'Admin in a day' training which are available on Github.

Last thing for this week is a tweet by Keith Whatling which shows a nice way to use the WITH function in Power Apps.

Introduction

Azure Functions can basically also be executed in Docker. During development you can also execute them locally. In this context, however, there is a problem in connection with Http triggers. Although the monthly Azure Functions Webcast (issue 20.02.2020) announced improvements in the area of Kubernetes Deployments, no further information is available or I could not find it.

Therefore this article shows how to use Azure Functions with a Http Trigger Docker.

Read more →

Einleitung

Azure Functions können grundsätzlich auch in Docker ausgeführt werden. Während der Entwicklung kann man diese auch lokal ausführen. In diesem Kontext kommt es aber in Verbindung mit Http Triggern zu einem Problem. Obwohl im monatlich stattfindenden Azure Functions Webcast (Ausgabe 20.02.2020) Verbesserungen im Bereich von Kubernetes Deployments angekündigt wurden, sind dazu bisher keine weiteren Informationen verfügbar bzw. ich habe diese nicht finden können.

Daher zeigt dieser Artikel wie man Azure Functions mit einem Http Trigger Docker betreiben kann.

Read more →

Interested in Durable Functions? Have a look at »Durable Functions #9: Raise Events / Human Interaction Pattern« by Marc Duiker.

Ever wondered whether everyone has an internal monologue? Doesn't look like it but a have a look at »Today I Learned That Not Everyone Has An Internal Monologue And It Has Ruined My Day« for further details.

This is one I still need to watch myself but I sounds very interesting. »Build Serverless Apps with Blazor« explains how to build serverless apps using Azure Functions together with Blazor.

Jeff Hollan tweeted about about Buccaneer which is generator for OpenAPI definitions out of .NET Core 3.1 projects.

If you are still lacking good content to read in 2020, what about 9 books about Azure? After reading and understanding all books mentioned in »The Top 9 Microsoft Azure Books You Need to Read in 2020« you should have a pretty deep knowledge about Azure.

Ever wondered »What is the most cost-effective way to run SQL and Windows Server in the cloud?« would be? Looking at this article you will have good starting point for your decision.

Sometimes components available in Azure seem to do similiar things. When choosing between the right way to handle logs, alerts, change feeds and webhooks and are not sure whether Event Grid could be right for you, you should have a look at »How Azure Event Grid is different from logs, alerts, change feeds and webhooks«.

Do you use your Azure shell on a daily base and wondered whether it would be possible to optimize your personal workflow? Then have a look at »Azure Cloud Shell + zsh, oh-my-zsh, tmux, and badass terminal!«.

Even though "Diving into Durable Entities" is a little bit older (September 2019) it is still a great introduction to Durable Entities in Durable Functions v2.

Using Azure API Management you can publish and manage your APIs. "How to publish your APIs with the new developer portal in Azure API Management" shows how to do this. Using Azure Functions together with Azure API Management is especially great because this way you can expose your Azure Functions as an API using OpenAPI to use them in Power Apps.

Looking for guidance on starting a greenfield project using React + .NET Core? Then you should definitely have a look at "Choosing a “Modern” React.js + .Net Core Stack" by jeremydmiller.

This weeks highlight is definitely "SameSite Cookies In A Nutshell". One might be thinking how this can be a highlight but this topic will become very important in the next days/weeks. After reading this article you will understand why. You should also have a look at the linked articles on SameSite cookies changes in Chrome 80+.

If you are looking for a way on how to use Event Grid, Azure Keyvault and Azure Functions all together then "Using Event Grid, Azure Keyvault and Azure Functions" is for you.

Seeing this sentence

consider the partner programs that you're involved in, and whether they are influencing any decisions you're making to the detriment of your customers

in "Leaving The AWS Partner Network" made me think whether this a valid point. My educated guess would be that yes is the answer to this question.

Steve Sanderson presented at .NET Conf on "Focus on Blazor". The code from his demo is now available online at SteveSandersonMS / presentation-2020-01-DotNetConf. Nice to see that using Blazor enables you to build cross-platform UI client.

Thorben Janssen wrote "Dual Writes – The Unknown Cause of Data Inconsistencies". If you never heard of dual write issues and think about using Microservices for specific scenarios which include data persistence then you definitely should read this article.

Yesterday evening I have been reading the blog post "Why we terminated our partnership with Microsoft - Re: Next decade of open source" by Paul Stovell who founded Octopus Deploy.

Figure: Octopus Deploy homepage, https://octopus.com/, 2020-01-28 20:10

My first thought was that Paul Stovell has a valid argument here. Nevertheless, I continued to think about his situation. At the same time I also read comments at Hacker News about it where I originally found the blog post.

In the end I came to the conclusion that the specific situation of Octopus Deploy is not comparable to other OSS projects. Octopus Deploy is not an OSS project, only many parts of it are OSS.

Therefore it can be said that Octopus Deploy is a competitor of Microsoft. So you can't accuse Microsoft to have torpedoed an OSS project, but only to have made the decision to launch an own product as an alternative to a competitor.

Conclusion

As a conclusion I can only say that one should not be discouraged by this blog post to be an active contributor in a .NET OSS project or even start one yourself.

So I personally cannot agree with Paul Stovell's conclusion.

Which brings me back to Aaron's post: it's not going to work.

Yes, it can happen that Microsoft will eventually come to the point of offering an alternative and thus become the de facto standard, but that doesn't necessarily have to happen. This can be seen in enough popular OSS .NET libraries.

Basically, my observation is that Microsoft has made a fundamental turnaround in its attitude towards OSS since Satya Nadella became CEO. Maybe Microsoft had the idea to push OSS out of the market a long time ago. In the last few years, however, I have observed that this behavior can no longer be seen.