.net

Ray tracing is getting a lot of hype lately. Lots of advanced rendering techniques are emerging that involve scene tracing of some kind, there are several frameworks for high-performance ray tracing, D3D12 is getting integrated support for ray tracing, and there’s a proposed Vulkan extension for the same.

Have you ever encountered an exception in your application while debugging, and wanted to know exactly what the state of the app was at that point in time? Or, you’re debugging async code and you want to know the context in which an exception was thrown? Now, with a new feature in IntelliTrace step-back, you can!

Given that, I decided to share my developer experience building, testing and deploying AWS Lambda functions in the .NET world. Not a “Hello World” example, but rather a real-world scenario, where some services integrate with each other. Since a Serverless function is a tiny piece of code in a much larger process, how can I test the flow on my development machine?

A few months back, I wrote a blog post that you guys seemed to love: List of the Best Free Visual Studio Extensions. Extending your IDE is the new black and we do too use a lot of extensions during our daily work. Previously, we used a lot of different development tools (alongside Visual Studio), but that changed when Microsoft launched Visual Studio Code. It hasn't replaced Visual Studio for us, but it's great for some aspects of our development process. We use Code for quick preview of files, writing markdown, other languages than C#, quick prototyping, and much more. This post is a summary of all of the different extensions we've found to make Code even better.