My Rants and Raves about technology, programming, everything else...
The next episode is now available! This time I'm talking to Shaun Walker. He's the developer responsible for the long-lived open source project, DotNetNuke! He's also created a new framework called Oqtane for Blazor.
He's been in the Microsoft-Open Source space for longer than almost anyone. We talk about being the maintainer for a project for 14 years, what "maintainer fatigue" is, and how being a maintainer has changed since 2002!
I hope you like it!
[UPDATE] After reviewing some of the code and talking with commenters, I agree that using HostServices for console apps is a bad idea. I've refactored this to use the host but not the HostService. I believe that the entire host is still useful for configuration, logging, and DI. See below for the latest changes:
I was at a customer site last week and a lot of their integration code is a set of console apps that are run on timers to import and export data. This isn't an uncommon use-case.
I've got a couple of these lying around myself. I realized that I didn't know of a good exemplar of doing simple console apps using .NET Core in a way that is closer to ASP.NET Core (e.g. dependency injection, lifetime management, cancellation, etc.). So I decided to re-write an old console app I have.
We talk about how he does this project while still holding on to a full-time job. He also delves into how CodePlex, OuterCurve, and the .NET Foundation has helped him build xUnit and maintain it all these years.
I hope you like it!
This new series is all about the open source projects you use every day. I am interviewing people who maintain those projects. I hope to get your favorite developers to talk about why Open Source is so important to them.
In this first episode, I talk with Jimmy Bogard about AutoMapper and how he built it so many years ago. I hope you like it!
I've been digging into Vue 3's beta for a while now. I like the new composition API, but it looks like there weren't that many quickstarts for getting a Vue 3 project going.
I decided to make a quick video to help you get started with it. The way that I create the project might change once Vue 3 gets to RC, but at least for two weeks, this should help some of you who want to get ahead of the curve. View it here:
I had great fun today talking with the netPonto User Group on Zoom. It was a fun group who had great questions about gRPC.
In this talk I talk about my view that gRPC is a great solution for certain scenarios and would normally be mixed with REST, GraphQL and SignalR. As promised here are the slides and code.
If you're not familiar with the .NET Foundation, it's a great organization that helps promote and fund the .NET community and open source projects. You can read more about it here if you're not familiar with it: https://dotnetfoundation.org/
I've decided to throw my hat into the ring for the board of the .NET Foundation. I believe that the board does great work fostering the next generation of .NET projects. Here's why I want to be on the board:
I'm passionate about .NET, but it's not the only community that I interact with. I am perplexed by the lack of .NET in non-enterprise environments (e.g. education, startups, etc.). I want to help drive the .NET Foundation to help projects that will help drive that adoption. Furthering the tools and projects that help improve the .NET community and welcome more members in with open arms.
In my spare time, I've been working on a micro-services example to try and make a minimum viable micro-service using ASP.NET Core. To make things that much harder, I've also decided to use Vue 3 for the front end. In for a penny, in for a pound.
After spending the last month with Vue 3 (or so), I've come away with some opinions that I thought I'd share. Some of these are because of the lack of support for Vue 3 for some of the common libraries I used, but in many ways it's a love letter to some of the features I really love. Her we go...
Developing on a Beta can be difficult. Lots of time there are inconsistencies between different versions of packages that are in different states. I haven't found this to be a particular problem with the Vue ecosystem.
I've been mulling this topic for a long time now. I had aimed to make this into one of my video rants, but I want to make sure the words I mean are the words I say. This is purely my view of the idea of privilege in my own life.
I consider myself a fairly successful person in software. This isn't how it was supposed to be. I was born into a family on welfare in the projects in New York City. My father's schizophrenia kept him from working most of the time. My mother, a teenage mother, waitressed to help make ends meet. Contrary to expectations were not the only white family in our apartment block. Our next door neighbor, a black woman, often watched me and my brother and sister when my mom had to work and my dad was having one of his bad days, which was often. We loved her like a second mother.
I wasn't destined for anything. Growing up poor in the United States is tough. Hard to see beyond the next paycheck and food stamps. I was just a kid so I didn't realize how difficult this was for my mother.
Yet another of my talks that resulted from being bored at home and on Twitter. I had a great time talking to this great group.
Even though it was a .NET group, they were open to me digging into why I think Vue is a great choice for the right project. They had great questions too!
As promised here are links from the talk: