Blog

I released another new extension for Visual Studio, and I want you to know about it!

I released a new extension for Visual Studio, and I want you to know about it!

You've got your own Visual Studio extension with custom CodeLens entries (because you used part I of this series), but now you find yourself needing to call code in the main extension host FROM the CodeLens Provider. How? Read on!

Many have tried generating Code Coverage metrics for .NET Framework applications, yet only few have succeeded. Even fewer choose to tell their story This is my success story.

What this did, however, is gave us cause for figuring out if CodeLens is enabled in Visual Studio at all (our provider doesn't do much good if everything is disabled).

Today, I spent a little bit of time figuring out how to get a proper CLA bot attached to some GitHub repositories. Gotta tell ya, it wasn't that hard, but I wanted to blog it anyway so I can refer back when I have to do it again in 5 years.

If you have your own Visual Studio extension, and you want to add your own custom CodeLens entries - I'm here to help, because I just (finally!) figured out how to do this (plus a few extras!)

I needed to be able to open an SSH tunnel in one of my Azure pipelines recently to get access to some databases hosted in AWS for running various integration tests.

I recently needed to figure out a way to send files to a third-party 'document manager' system using `HttpClient` in .NET 6.0. This 'document manager' system already had an API for uploading files, which we had previously gotten working in our teams Postman collection.