This video is in continuation of my last two video posts where we discussed some awesome visual studio tips which makes you super productive. In first video, we talked about tips related to Class and in second video, we discussed some other common tips for adding very common code snippets. Please find my previous two videos below
[Video] Visual Studio Tips to make you Super Productive
[Video] Visual Studio Tips to make you Super Productive – Part 2
In this video, we are going to discuss another 10 tips related to Visual Studio IDE which will help in day to day development, debugging, code review etc.
Use these tips in day to day activities and be few steps ahead 🙂
This video is in continuation of my previous video where we discussed few awesome visual studio tips related to class . Refer the link my previous video below here
Here I have discussed another set of tips that will add more power to you as a developer.
In this video, I have talked about five Visual Studio tips related to class which can save lots of time in your day to day programming.
Use these tricks and make yourself super productive.
Visual Studio is very Rich IDE and it provides in-numerous features that makes our day to day life easy. There are some very useful hot keys and tips which can increase our productivity significantly. Earlier I used few hot keys but recently I learned few which I found awesome which drastically reduce my time while writing/debugging/reviewing the code. So learn these and make a habit of these keys and feel super charged while writing code.
- While code review I find many time scattered and unaligned code which I hate. I use CTRL+K+D for aligning it.
- While debugging or testing the code, commenting/commenting codes are done a lot. Use CTRL+K+C/CTRL+K+U for the same.
- How do you up/down certain line of code. Select the code block and use ALT+up/down
- You have a used a lot F12 to go to Definition of class. Use CTRL – to go back.
- How do you resolve the classes by mouse click. Use CTRL+. to resolve it quickly.
- Refactoring is very important. Use CTRL+R+M for extracting a method.
- Find All References -> Use Shift + F12. Very helpful while debugging and fixing bugs.
- Want to put few lines of code in try block. Try Ctrl + K + S, it provides lot more options
- Ever tried selecting a rectangle code. Use ALT click drag.
- Lots of code in a single file. Use CTRL + M + O and CTRL + M + X in collapse/expand code groups like regions, methods etc.
- Lots of code and there are no groups. Use CTRL+M+H/CTRL+M+U
- Another super sweet. ALT+F4 to close the window.
Try using the above in your day to day coding and be more productive.
This post is second part of my previous post where we discussed six tips to improve the performance of ASP.NET applications. In this post, we are going to discuss six more tips that could be another round a booster for your application performance. The link of previous post is below.
12 tips to increase the performance of ASP.NET application drastically – Part 1
- Make your page asynchronous
IIS uses CLR thread pool to get a thread that processes a request that comes to the application. Say, if there are currently twenty threads available in pool, it means only twenty request can be served in parallel and if request processing takes some time then it could turn into disaster if hundred odd request are bombarded in few milliseconds. In this case…Read complete post on Infragistics blog
Building web application and hosting it on a web server is insanely easy with ASP.NET and IIS. But there are lots of opportunities and hidden configurations which can be tweaked that can make it high performance web application. In this series post, we are going to discuss some of the most unused or ignored tricks which can be easily applied to any web application.
- Kernel mode cache – It is one of the primary tools widely used for writing making web application faster. But most of the times, we don’t use it optimally and just leave some major benefits. As each asp.net request goes through various stages, we can implement caching at various level as belowWe can see that request is first received by http.sys so if it is cached at kernel level, then we can save most of the time spent on server as http.sys is a http listener which sits in OS kernel…Read complete post on Infragistics blog