My Rants and Raves about technology, programming, everything else...
They finally posted the video, so if you want to see the talk, here is your chance:
As promised, here are links to the code and slides from the talk:
Unless you you haven't been paying attention to me or my blog the last three years, you know that I've been working on a film. The feature-length documentary is about my love for the software industry and the lack of diversity that I see in it.
I am trying to raise enough money to finish the film. It's been a three-year project where I've interviewed over fifty people across several continents. I've talked to developers, educators, and industry leaders about what there is to love about the job that most of us do. We've edited the film and had a couple of test screenings so we're close to being done.
In fact, I shot so much footage that many of the topics I wanted to covered got cut from the film. That has left me with the opportunity to make some short films that covered several of these topics. The first of these is now available:
Endpoint Routing was introduced in ASP.NET Core 2.2 but has been made a first class citizen of ASP.NET Core in 3.0. While you're old projects will continue to work without it, upgrading to Endpoint Routing will improve your applications.
Endpoint Routing is a system to handle routing across different middleware systems (e.g. MVC, Razor Pages, Blazor, SignalR and gRPC). By having endpoints that work with each other, you can think of a system more holistically then having terminal middleware that don't talk to each other. Let's see what that actually means in practice.
If you've seen the new project template, you've probably already noticed that setting up RazorPages and MVC look a bit different. First in the ConfigureServices:
I'm finally getting around to looking at updating my examples and courses to 3.0. This post is based on .NET Core Preview 8 so this might change in the future.
There are a number of great walkthroughs for moving your ASP.NET Core 2.x projects to 3.0. So I don't want to repeat that. Instead, I want to talk about what's happening, not just a list of things to do.
To discuss these changes, i'll talk about a project I'm current converting (CoreCodeCamp which is the basis for the Atlanta Code Camp), though it's a branch that likely won't be deployed until after the event.
If you've viewed my new "Designing RESTful Web APIs" course on Pluralsight, you've already encountered my small API that I use as an exammple. While the course is platform agnostic, i'll admit that I built it with ASP.NET Core (2.2).
For this new project, I decided that running in a container would be useful as it's pretty self-contained and should just return to it's initial state when the container is restarted. While I won't be releasing that source, I did learn a lot about debugging in a container that I thought I'd share.
I started this new project and opted into using Docker in the project:
I was talking with David Berry when we both heard the news about MSDN Magazine shutting down after the November issue. I'm really saddened by it.
The reality is that MSDN Magazine had a dramatic impact on my career, both as a reader and an author. I'd like to share my memories of it.
Years back (I think 1998) I went to one of my first development conferences in Boston. There I saw Chris Sells, Don Box, and Jeffrey Richter for the first time. I left there wanting to figure out how to speak at conferences. I loved the idea of sharing my experience with others. Code camps and user groups were in their infantcy so I didn't know of another way to scratch that itch.
I'm planning on talking about gRPC and Vue.js (though the speakers haven't been selected yet). I'm looking forward to being at the entire event this year since I'm not travelling.
This year's event will be held on September 14th, 2019 at:
I've been updating the CoreCodeCamp project (the basis for the Atlanta Code Camp's website) for this year's Code Camp. Most of the changes are under the covers, but I wanted to talk about what I learned.
The goal of the upgrade was two-fold: upgrade to .NET Core 2.2; and move the Vue.js code to Vue CLI (to improve loading performance). It also allowed me to do some rudamentary clean I've wanted to do. On to the lessons...
In the past few years, I've run the Atlanta Code Camp website by the seat of my pants...and it cost me. On several occassions, pushing a new build to the website brought down the website (sometimes my fault; sometimes Azure's fault). I was convinced I needed to use Azure Development Slots to address this.
I started writing services in websites back in the .NET 1.0 days. Originally I was doing just POX (Plain Old XML) services in a very crude way so we could get the job done for our internal systems back in the early 2000's.
This means I've been through the "new tech" crazy with services for a long time. I've spent much of the last year digging into different tech for services to interact with websites (though many of the same issues are for rich clients and IoT). I'm not done and don't know how right my assumptions are yet, but I thought I'd try to start a conversation.
While I've lived through POX, SOAP, and REST...I don't think this is another wave. I think this is a widening of options for services. But what does the service ecosystem look like right now? (Caveat: I'm going to miss your favorite idea, so feel free to add to the discussion below.)
I've been updating the Atlanta Code Camp website to improve our administration workflow. With the Call for Speakers coming up soon, I wanted to make sure we had a good way of picking only the best talks.
One of the things I've done is move it to a Single App with Vuex at the center of it. But I ran into an oddity with Vuex that I thought I'd share.
Much of the work I do in Vuex has to do with adding, updating and removing objects from the state. That works exactly the way I would expect. For example, I have a lot of mutations that looks like this: