Why? Because they help me implement features faster. But it wasn’t always that way. Let me show you how I went from aversion to actually enjoying tests, and why they’re so helpful now. Bad experience My first experience with tests was awful. Back in 2015, I worked on a team that had strict code coverage requirements. The workflow looked like this: They didn’t have integration tests; unit tests were mostly trivial, with tons of manually initialized mocks. ...
I will show you ways to read string data from arbitrary .NET assembly in case when you don’t have: Reflection, i.e when you operate from a trimmed or AOTed application Full set of app dependencies. This is conceptionally wrong - why do we need to load everything, when we only need raw data from a library, also, I wanted a way to read data from damaged distributions. Let’s imagine we have an assembly, where we have this code: ...
I have a Windows desktop application that I distribute using MSIX packages, making them easily installable and automatically updated on modern Windows machines. To create such a package, the most straightforward method is to use the Windows Application Packaging (WAP) project, although it does have its quirks. Additionally, I have a utility project that doesn’t require access to Windows APIs but needs to support trimming and be as compact as possible. As a result, I ended up with this dependency graph and the following MSB6006 error: ...
Recently, I came across a one-year-old Youtube tutorial, that showed how to run ChatGPT on my own data in ~15 minutes. That sparked my interest, I thought - what if I fed ChatGPT with my codebase, so it could respond to queries like: Where in the code is the order total compared to what’s returned by the vendor? And it would show me code fragments with class names (I’m in C#). Or: ...
A couple of years ago I crafted an internal-use utility for one of my clients that uses Azure Static Web Apps with Blazor and some Functions. That worked well, but the client asked to extend functionality, so I decided to refresh the code along the way. Back in the day, I wrote the utility using .NET 6 and in-process functions, since the out-of-process mode was not yet available. The current .NET 8 shifted focus to the out-of-process mode, which is much better and less tied to Azure SDK code. However, according to the Azure Functions docs, they still supports in-process mode, so I anticipated an easy migration. Well, I totally misjudged that! ...