Introducing Practical .NET Insider -- Visual Studio Magazine

Desmond File

Introducing Practical .NET Insider

Visual Studio Magazine Tools Editor and Practical .NET columnist Peter Vogel is a busy man -- and it's all his own fault. Last month, for instance, Peter approached me about writing an occasional series of opinion columns based on questions and topics he runs across in his consulting work. Unlike the how-to flavored fare of his Practical .NET print and Web columns, these columns are intended to explore assumptions and pose questions.

The result is Practical .NET Insider. You can read Peter's first exploration -- focused on SOA build outs -- here. Next month, we'll publish Peter's look at debugging and what it takes to be good at it.

Posted by Michael Desmond on 06/27/2011

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.