Learn how error monitoring with Sentry closes the gap between the product team and your customers. With Sentry, you can focus on what you do best: building and scaling software that makes your users’ lives better.

Introduction

Code Refactoring has always been a challenge for developers. This is one of the major skills that a developer should have in order to write optimized, clean, and fast code. There were third party tools available to help you achieve this, but none have shown the capability that Visual Studio 2015 has come up with.

Visual Studio has always offered code refactoring techniques in tidbits, but the latest version of Visual Studio provides a unique experience altogether to achieve refactoring. There are many features that refactoring of code in Visual Studio provides. We’ll cover a few of them like inline temporary variable and introduce local. Refactoring w.r.t. inline temporary variable and introduce local is not only limited to C# but VB developers can also leverage this feature. We’ll cover the topic with one small method as an example and try to optimize it as far as we can. One thing to make note of is that code refactoring software and techniques are only meant for sharp developers. If you don’t have an idea what the new code will do, and it looks strange to you, you should never try it.

Case Study

I am taking an example of MyProducts class that we created in an earlier section.

We’ll add one more method to this class. The objective of that method will be to return all products from the product list whose price is greater than 30,000. I am trying to keep the logic and method very simple for the sake of understanding. I have kept the name of this method as FetchProduct(). Notice that we already had two methods with the same name. Now this will also work as an overload to the FetchProduct() method.

The above-mentioned method is very simple in nature and contains a LINQ query that fetches products having a price greater than 30,000. When we call this method from Program.cs and iterate over the elements we get the following result.

So, our method is working fine. The question is how much further we can optimize this method. When you click in between products variable, the light bulb icon will show up with some suggestions that you can apply to this line to optimize.

Now inline temporary variables come into the picture. The light bulb icon says to remove this variable and bring that code to a single line. When you preview the changes that this code assistance is suggesting you get following preview window.

It shows that the temporary products variable will be replaced with productList itself, therefore helping us to save a number of lines as well as memory allocation for a variable. Click on apply changes and you’ll get the refactored code.

Now, can this code be further refactored? You can get help from light bulb icon. Either click in between the productList variable or right click on the productList variable and open Quick Actions from the context menu.

We see here, productList is also a temporary variable and it is suggested to remove that too. Let's preview changes and apply them to get more optimized code. Doing this, the productList variable will be replaced by a single return statement, but you’ll notice an error here. If you remember, I said that code refactoring is for intelligent and sharp developers. We see here that while refactoring the code, LINQ query is not encapsulated in the bracket and the ToList() method is directly applied to "p" variable. We have to rectify this by putting brackets around the LINQ query. This was one of the scenarios, and you may face many like it. So you have to be sure about the change that you are about to do. Visual Studio only suggests, it does not code for you.

Now we have a single return statement. Our code has reduced to just one line and we also saved memory by ignoring temporary variables. This certainly makes the code faster, but can we further optimize this method? Let’s take a shot and click on the return statement. You’ll see the light bulb icon again shows up with some suggestions.

It says that the method could be converted to an expression bodied member. Let's preview the change.

The preview says that the method is converted into an expression. Looking at this, I do not find any issue. So, we can certainly opt for this option for the sake of refactoring. Press apply changes and we get the following code.

Now if you try to further optimize this method, you’ll not find much scope.

Conclusion

This was just a small example that I showed on how you can leverage the capability of Visual Studio 2015 in optimizing your code. In the next section of this series, I’ll be covering topics like debugging features in Visual Studio 2015.

For more technical articles you can reach out to my personal blog, CodeTeddy.