Sunday, October 29, 2017

Improving Code Quality with Visual Studio Code Metrics

Visual Studio 2017 code metrics is a set of important software tools for measuring the quality, code maintainability, and complexity of code written by a developer. These metrics also provide developers better insight into the code they have written by understanding the types of classes/methods/modules that should be reworked and thoroughly tested, identify potential risks, current state of code, track progress of development, and so forth. Code metrics are available with the VS Community, Premium, and Ultimate editions. Developers also can download the extension and install it in Visual Studio. It's a good practice to use code metrics to validate code; it will not only improve code quality but also make your application maintainable and less complex.

More

Friday, October 20, 2017

Visual Studio Diagnostic Tools Breakdown

Performance of any application is top priority from a customer perspective. For a developer, identifying performance issues prior to production deployment is a difficult task indeed. Visual Studio 2015 Diagnostic Tools made it easier for developers to have a performance analysis and review before the application goes live. As a Visual Studio 2015 developer, you can get detailed application insights while you are debugging code.

More

Tuesday, October 10, 2017

Integrating NLog with Visual Studio


NLog is an open source logging framework that enables you to add high-quality logs and sophisticated tracing for your .NET application. It's a free framework, cross-platform, and easy to configure and extend. NLog comes with excellent support for log routing and management capabilities. NLog can log your application data and create logs regardless of the size and complexity of your application.

More

Tuesday, October 03, 2017

Creating and Reading Application Logs in .NET

An error-free piece of code theoretically should exist, but, in reality, it's almost impossible to test whether an application works under every situation. When errors occur, there are different ways to handle them. As a developer, it's best practice to detect and catch errors and log them as well. For example, performance problems may occur only when your application is dealing with a large data load. To diagnose these errors in a production environment, you need to log errors automatically so they can be reviewed and analyzed at a later time to fix the issue. The .NET Framework provides a wide range of logging options; Windows System Event Log is one of those from your .NET application. As a developer, you can write code to log an error in the Event viewer and gather information about the software problems and monitor system events.

More

Mocking API Responses in Azure API Management Portal

A mock API imitates a real API call by providing a realistic JSON or XML response to the requester. Mock APIs can be designed on a developer...