Introduction to a .NET Series
Now that I've blown the rust off my Microsoft .NET skills at my former employer, I'd like to share a few things I've learned along the way. I will be…
Now that I've blown the rust off my Microsoft .NET skills at my former employer, I'd like to share a few things I've learned along the way. I will be…
I'm excited to begin a demo project applying IDesign to .NET. This series will follow my progress. Along the way, I'll be using a minimal api to bridge from the…
Recently, I've been introduced to the IDesign methodology. While I have yet to implement it, or see it in action, I do have some comments based on my introduction to…
An example of deploying a .NET MinimalAPI to Azure via GitHub Actions
This is the test and publish stage article in a series covering continuous integration, CI, for .NET.
This is the build stage article in a series covering continuous integration, CI, for .NET.
This is the first introductory article in a series covering continuous integration, CI, for .NET.
When your systems have grown and weaknesses in the CI-CD pipelines become apparent, it's time to optimize. You need to know what to optimize and how to track improvements.
.NET 7 brings some wonderful bells and whistles for APIs. This article will cover an example of a simple, minimal API you can easily examine via Swagger and OpenAPI.
When you're spinning up an app quickly, perhaps a POC, perhaps as the beginnings of a more complex app, it's helpful to have mock data for your app to ingest, as a faster method than EF and creating database tables. This approach uses Microsoft's chained configuration to ingest json data to populate the app.
Questions often asked when debugging issues around .NET and chained configuration, especially for generic host builders using CreateDefaultBuilder