If are debugging through a class/library you've gone through many many times. You know it works, it's solid. So stop wasting time going through it. Place a

[System.Diagnostics.DebuggerStepThrough()] for C#
or
<System.Diagnostics.DebuggerStepThrough()> for VB.NET

This attribute tells Visual Studio to skip the class while debugging through code.

When you create an ADO.NET DataReader object, specify the CommandBehavior.CloseConnection enumeration in your call to ExecuteReader. This ensures that when you close the DataReader, the SQL connection is also closed. This is especially helpful when you return a DataReader from a function, and you do not have control over the calling code. If the caller forgets to close the connection but closes the reader, both are closed when the DataReader is created by using CommandBehavior.CloseConnection.

ChEeRs!!!

Most ASP.NET developers use the standard F5 (Debug/Start Debugging) to start debugging from Visual Studio. However, there is a much faster way to start debugging if you already have an instance of your web application running. Just attach to it instead:

 * Choose Debug/Attach to Process.
 * Select the "aspnet_wp.exe" process and choose Attach.

 Keyboard Shortcut: * ALT+D, P, "as", Enter.

Debugging this way is faster because you skip the often-lengthy compilation step, and you don't have to navigate from the start page to the actual page that you want to debug

Genie!!!

System.Diagnostics.Stopwatch is a replacement for what most people probably do to identify the time spent on excecuting a method. The process usually goes something like: create a DateTime.Now value at the start and then subtract the ending DateTime.Now to get the TimeDuration value that elapsed. 

As an alternative, the Stopwatch class was built using low-level API calls, with less overhead than other .NET methods. If the hardware and Windows version of the computer support a high-resolution performance counter, it will use this counter instead of the standard PC clock. 

Here is a simple example: 

System.Diagnostics.Stopwatch watch = new System.Diagnostics.Stopwatch();

watch.Start();

//do my stuff

...

watch.Stop();

MessageBox.Show("Time spent: " + watch.Elapsed.ToString());

Assume in the master page, we have a user control which we need to access and set its visiblity from content page. We create a public property in the master page called controlVisiblity

public bool LoginControlVisible { 
get{ return LoginControl.Visible;}
set{  LoginControl.Visible = value;}
}

To gain access to the master page file from the content page, you just need to add the below directive to the content page
'<'% @ MasterType VirtualPath=”~/siteMaster.master” %'>'
When ASP.NET realizes the existance of this directive, it generates a strongly typed property “Master”. this property will give you access to the MasterPage file. So directly in the content page code behind you would use the below instead of trying to use the FindControl method.

Master.LoginControlVisible = true;
or
Master.LoginControlVisible = false;

ChEeRs!!!

Securitypermission Perm = new Securitypermission (SecurityPermissionFlag.UnmanagedCode);

Perm.deny();

Perm.Assert();

This class is used to check whether you have permissions to execute an unmanaged code or not. If you don’t have permissions then you need to provide the application with necessary permissions otherwise this will throw an error.

This procedure is called the declarative security code writing.

[SecurityPermission(SecurityAction.Assert, Flags =

       SecurityPermissionFlag.UnmanagedCode)]

Public void execUnmanagedCode()

{

      // the code goes here./….. this is another method to execute the code.

Private Function ImportLeadFile(ByVal projectfile As String, ByVal sLeadFile As String, ByVal DATABASE As String) As Boolean

        Dim objConn As nsSqlClient.SqlConnection

        Dim ds As New DataSet

        Dim m_strConnection As String = "server=NINEL-D246655F1;Initial Catalog=TimeControl;user id=timeuser;password=timeuser;"

        objConn = New nsSqlClient.SqlConnection

        objConn.ConnectionString = m_strConnection

        objConn.Open()

        ' Make sure the .CSV file exists:

        If File.Exists(sLeadFile) Then

            Try

                ' ------ Load the data from the .CSV file: ----------

                Dim strSQL As String

                strSQL = "Select * " & _

                       " INTO " & DATABASE & ".dbo.[List_staging] " & _

                      "FROM  OPENROWSET('MSDASQL','Driver={Microsoft Text Driver (*.txt; *.csv)}; DEFAULTDIR=C:\VoicenetSQL\project\tampa\Politic\" & projectfile & "; Extensions=CSV; HDR=No;','SELECT * FROM at1008.csv') "

                 Dim objCommand As nsSqlClient.SqlCommand

                objCommand = New nsSqlClient.SqlCommand(strSQL, objConn)

                objCommand.CommandText = strSQL

                objCommand.ExecuteNonQuery()

                objConn.Close()

            Catch ex As Exception

                sResultText = sResultText & "<BR>" & ex.Message

            End Try

        End If

End Function

Genie!!!