If you’re building modern .NET Aspire apps, you’re probably familiar with how service names and resource identifiers are often passed around as string literals, things like "apiservice" or "storage". But these magic strings can lead to headaches: typos, duplication, poor discoverability, and painful refactoring.
Thankfully, there’s a clean and safe way to centralize and manage these identifiers using a shared constants class, removing “secret strings” from your Aspire project. 💥
It seems increasingly clear that Semantic Kernel is where Microsoft is investing for building modern, robust AI applications. In fact, Microsoft has stated as much: “Semantic Kernel (is) central to Microsoft’s enterprise AI story”.
In typical Microsoft fashion, they offer several seemingly competing options for developers to choose from, such as AutoGen, Microsoft.Extensions.AI, and probably a few others I’m forgetting right now. This variety doesn’t make it any easier for .
Have you ever had a moment of inspiration, an idea you wanted to test in C#, but didn’t want to spin up a full project just to run a few lines of code? Same here.
Well, with .NET 10 Preview 4, that pain is going away. Say hello to the new dotnet run app.cs feature.
It’s like C# finally took a page from Python and JavaScript, languages that have long made it easy to run a file with a single command.