Profiling gathers information about an executing application, allowing you to determine those improvements that are required in your application.
Ten reasons why you should bother profiling your .NET code
1) Focus on portions of your .NET code that really require attention
2) Identify code blocks with performance issues
3) Compare alternative approaches
4) Get accurate code execution response times
5) Avoid guessing performance issues
6) Visualize performance and memory usage
7) Track the lifecycle of your .NET objects
8) Avoid unnecessary loading or initialization of your program
9) Optimize your looping constructs in .NET
10) Identify memory leaks in your application

How to profile your .NET code?

• CLR Profiler
• Using PerfMon

Today I had some problems with a report solution created in Visual Studio 2005:
After I got the latest version out of SourceSafe, I could not open it anymore. The error message was "Project item '4294967294' does not represent a file."
Searching for this error on the internet I came to this solution:

- Open the .rptproj file in notepad (or another text editor) and delete the line that begins with "<State>$base64$"

       Sometime in notepad you may not view complete data, so try to open in CMD -> Edit window.
- Open the solution
- Delete the source control bindings
- Add it to source control again
- Done!

Yesterday I got this error message while running Asp.net application in Visual studio 2005

---------------------------
ASP.NET Development Server
---------------------------
ASP.NET Development Server failed to start listening on port 1085.
Error message:
An attempt was made to access a socket in a way forbidden by its access permissions
---------------------------
OK  
---------------------------

By default the web application uses ASP.NET development server not the IIS. We
can change it to IIS by selecting Project Properties->Web Tab. There we can
create the virtual directory too.
The error must be specifying some port. I try to use some tools like TcpView from
Sysinternals (http://www.sysinternals.com/Utilities/TcpView.html) to check that
port is used by some other process. Normally development server will take the
free port while running the application.

Following query will display stored procedure content through Query.

    SELECT ROUTINE_DEFINITION
    FROM INFORMATION_SCHEMA.ROUTINES
    WHERE ROUTINE_NAME='SPLocationGetByID' AND ROUTINE_TYPE='PROCEDURE';

Good to read basic of SQL Join at

http://en.wikipedia.org/wiki/Join_(SQL)#Inner_join

Following vbscript snippet call web service with parameter.

Dim oXMLDoc, oXMLHTTP
Sub btnclick
Set oXMLHTTP = CreateObject("MSXML2.XMLHTTP.4.0")
Set oXMLDoc = CreateObject("MSXML2.DOMDocument")
Msgbox("Calling WebService To Approve Leave")
oXMLHTTP.onreadystatechange = getRef("HandleStateChange")

Dim strEnvelope

strEnvelope = "userId=1"
call oXMLHTTP.open("POST","http://localhost/MerchantServerWS/MCService.asmx/GetName",true)
call oXMLHTTP.setRequestHeader("Content-Type","application/x-www-form-urlencoded")
'call oXMLHTTP.setRequestHeader("SOAPAction","http://localhost/MerchantServerWS/MCService.asmx?wsdl")

call oXMLHTTP.send(strEnvelope)
End Sub
Sub HandleStateChange
if(oXMLHTTP.readyState = 4) then
dim szResponse: szResponse = oXMLHTTP.responseText
call oXMLDoc.loadXML(szResponse)
if(oXMLDoc.parseError.errorCode <> 0) then
call msgbox("ERROR")
call msgbox(oXMLHTTP.responseText)
call msgbox(oXMLDoc.parseError.reason)
else
call msgbox( oXMLDoc.getElementsByTagName("string")(0).childNodes(0).text)
end if
end if
End Sub

The individual cells in a DataTable can have a null value in the form of System.DbNull.Value. If the DataTable is created by querying a database through ADO.NET, you can write the SQL statement in a way eliminates nulls. It could look like this “SELECT isnull(name, 'n/a') AS name FROM products”.

However, there can be scenarios where you don’t have the chance to manipulate the DataTable before you use it. Such a scenario have I recently been involved in and the problem was that the data retrieved from a database could contain nulls in any of the integer type columns. If I then bind the DataTable to a GridView in ASP.NET, I had to do a lot of workarounds to calculate footers and other values based on those columns.

Instead of doing the workarounds in a lot of different places in the code, I decided it was a better idea to clean the DataTable for nulls before it is used. That led to the CleanDataTable method below, that replaces null values with zeros for a few integer type columns.

/// <summary>

/// In the case of null values in a data table, this method

/// will turn all nulls into zeros instead.

/// </summary>

public static DataTable CleanDataTable(DataTable dt)

{

for (int a = 0; a < dt.Rows.Count; a++)

{

for (int i = 0; i < dt.Columns.Count; i++)

{

if (dt.Rows[a][i] == DBNull.Value)

{

Type type = dt.Columns[i].DataType;

if (type == typeof(int) || type == typeof(float) || type == typeof(double))

{

dt.Columns[i].ReadOnly = false;

dt.Rows[a][i] = 0.0F;

}

}

}

}

return dt;

}

The point is that you only have to clean it once to avoid any workaround for handling null values.