Visual studio and .NET tip 7:- Drag and drop code from tool box
By Shivprasad Koirala
As a developer you always need some common codes again and again. Rather than writing those common codes from scratch you would like to get them easily from some handy place.
Visual studio and .NET tip 7:- Drag and drop code from tool box
As a developer you always need some common codes again and again. Rather than writing
those common codes from scratch you would like to get them easily from some handy
place.
For instance when using ADO.NET you always need to write code for opening the connection
objects and closing them. So rather than writing this code again and again if
you can get them from some common place life would be much easy.
SqlConnection oConnection = new
SqlConnection(ConfigurationSettings.AppSettings["ConnString"]);
oConnection.Open();
// Write your custom logic here
oConnection.Close();
For a developer the handiest place is the tool box and the good news is you can select
the code and pin in it on to the tool box. When needed you can select the code
from tool box and drag them on to your coding area.

You can also better organize your code by creating tabs on the toolbox for better
management as shown in the below figure.

Video for the above tip and trick:- http://www.youtube.com/watch?v=dIigx1VPfdg
Related FAQs
When we select source code in visual studio it selects the complete source code , but what if we want to select the code in a rectangular manner?
In this section we will see a very interesting and useful trick of visual studio called the extract method.
Now many times as a .NET developer we need connection strings to connect to databases. Connection string are long and cryptic and very difficult to remember. In this tip we will see a easy way of getting connection strings.
Many times we write comments in code to remind about certain tasks to be performed later and then we forget about the same as the comments gets lost in those million lines code.
Many times due to project pressure and lazy attitude you violate encapsulation and create public variables for classes as shown below. Even though your inner heart knows that the best practice is to create set and get property function but your lazy attitude overrules it.
While debugging you often want to skip debugging on certain lines of code. For instance in the below code you have set the debug point to the first line, you would like to skip the in between lines and jump directly to “console.writeline” step.
Visual studio and .NET tip 7:- Drag and drop code from tool box (636 Views)