Call: GetTitleCase("RAJESH GOEL")
using System.Globalization;
using System.Threading;
private string GetTitleCase(string Text)
{
CultureInfo cultureInfo = Thread.CurrentThread.CurrentCulture;
TextInfo textInfo = cultureInfo.TextInfo;
return textInfo.ToTitleCase(Text.ToLower());
}
Result : Rajesh Goel
Friday, July 24, 2009
Regex Expressions
Replace all special characters from string using REGEX EXPRESSION
If you want to replace special characters from string, then just need to use below expressio:
Regex.Replace(value, @"[^\w-\/]", "-")
Like:
ReplaceSpecialCharacter("(you don't need to insta/ll the software and you don't need--to register)")
private string ReplaceSpecialCharacter(string value)
{
return Regex.Replace(value, @"[^\w-\/]", "-");
}
Result:
-you-don-t-need-to-insta/ll-the-software-and-you-don-t-need--to-register-
If you want to replace special characters from string, then just need to use below expressio:
Regex.Replace(value, @"[^\w-\/]", "-")
Like:
ReplaceSpecialCharacter("(you don't need to insta/ll the software and you don't need--to register)")
private string ReplaceSpecialCharacter(string value)
{
return Regex.Replace(value, @"[^\w-\/]", "-");
}
Result:
-you-don-t-need-to-insta/ll-the-software-and-you-don-t-need--to-register-
Wednesday, July 22, 2009
Different type of errors in ASP.Net
Object must implement IConvertible

Error Code:
StringBuilder itemNumbers = new StringBuilder();
DataView DV = DS.Tables["Products"].DefaultView;
int DVRowCount = DV.Table.Rows.Count;
if (DVRowCount > 0)
{
foreach (DataRow dr in DV.Table.Rows)
{
sItemNumbers.Append(Convert.ToString(dr["Prod_Id"]));
sItemNumbers.Append(",");
}
ArrayList oArrParam = new ArrayList();
oArrParam.Add(new Parameter("@itemNumbers", itemNumbers, ParamDirection.Input, DbType.String));
}
The problem: you need to convert string builder value to string. The code should look like this:
ArrayList oArrParam = new ArrayList();
oArrParam.Add(new Parameter("@itemNumbers", itemNumbers.ToString(), ParamDirection.Input, DbType.String));}
Error Code:
StringBuilder itemNumbers = new StringBuilder();
DataView DV = DS.Tables["Products"].DefaultView;
int DVRowCount = DV.Table.Rows.Count;
if (DVRowCount > 0)
{
foreach (DataRow dr in DV.Table.Rows)
{
sItemNumbers.Append(Convert.ToString(dr["Prod_Id"]));
sItemNumbers.Append(",");
}
ArrayList oArrParam = new ArrayList();
oArrParam.Add(new Parameter("@itemNumbers", itemNumbers, ParamDirection.Input, DbType.String));
}
The problem: you need to convert string builder value to string. The code should look like this:
ArrayList oArrParam = new ArrayList();
oArrParam.Add(new Parameter("@itemNumbers", itemNumbers.ToString(), ParamDirection.Input, DbType.String));}
Monday, July 20, 2009
Saturday, July 18, 2009
Keyboard shortcuts for ASP.NET
Build keywords
F5 - Start Debugging
Ctrl + F5 - Start Without debugging
Shift + F5 - Stop Debuggig
Ctrl + Shift + B - Builds your project
Ctrl + Break - To stop bild process
Comment keyword
Ctrl+ K +C - Comments Selection
Ctrl+ K + U - Uncomments Selection
Right Click keyword
Shift + F10
Collapse/Expand keyword
Ctrl + M + O - Collapse to Definitions
Ctrl + M + L - Collapse All and Expand All
Ctrl + M + M - Collapse and Expand a Single region
Find keyword
Ctrl-F/Ctrl + Shift + F : Shows "Find" dialog
Ctrl-H/Ctrl + Shift + H : Shows "Replace" dialog
Ctrl-G : Shows "Find" line number dialog
Breakpoint keyword
F9 : Toggle breakpoints
Ctrl + Shift + F9 : Clears all breakpoints
Ctrl + D + B : Open breakpoint window for function - need to specify function name
Windows keyword
Ctrl + D + B : Open breakpoints window
Ctrl + D + I : Open immediate window
Full Screen keyword
Shift + Alt + Enter :- To see full screen view
Scroll forward/backwards
Ctrl-Tab: Scroll forward through open windows
Ctrl-Shift-Tab: Scroll backwards through open windows
Attach the debugger to a process
Ctrl-Alt-P : This is insanely useful for debugging ASP.NET web sites without having to start the project in debug mode
Code/Designer windows
F7 : Show the code windows
Shift-F7 : Show the designer window
Bookmark keyword
Ctrl + B + T : Toggle code bookmark
Ctrl + B + E : Enable bookmark
Ctrl + B + P : Previous bookmark
Ctrl + B + N : Next bookmark
Ctrl + B + C : Clear bookmark
Open windows keyword
F4 :- Opens the Properties window
Ctrl + Alt + X :- Opens the Toolbar window
Ctrl + W + S :- Opens the Solution Explorer window
Ctrl + W + L :- Opens the Server Explorer window
Ctrl + W + C :- Opens the Class Viewer window
Ctrl + Shift + E :- Opens the Resource view window
Toggle character keyword
Ctrl + T : Toggle character
Snippet keyword
Ctrl + K + X - Insert Snippet
Intellisence keyword
Ctrl + Space - Intellisence
Line operations keyword
Ctrl + Enter - Insert a new line above the current line
Ctrl + x/Ctrl + L - Delete current line
Undo/Redo keyword
Ctrl-Z / Ctrl-Y: Undo typing / Redo typing
Navigate Forward/Backward
Ctrl + - : Navigate Backward
Ctrl + Shift + -: Navigate Forward
F5 - Start Debugging
Ctrl + F5 - Start Without debugging
Shift + F5 - Stop Debuggig
Ctrl + Shift + B - Builds your project
Ctrl + Break - To stop bild process
Comment keyword
Ctrl+ K +C - Comments Selection
Ctrl+ K + U - Uncomments Selection
Right Click keyword
Shift + F10
Collapse/Expand keyword
Ctrl + M + O - Collapse to Definitions
Ctrl + M + L - Collapse All and Expand All
Ctrl + M + M - Collapse and Expand a Single region
Find keyword
Ctrl-F/Ctrl + Shift + F : Shows "Find" dialog
Ctrl-H/Ctrl + Shift + H : Shows "Replace" dialog
Ctrl-G : Shows "Find" line number dialog
Breakpoint keyword
F9 : Toggle breakpoints
Ctrl + Shift + F9 : Clears all breakpoints
Ctrl + D + B : Open breakpoint window for function - need to specify function name
Windows keyword
Ctrl + D + B : Open breakpoints window
Ctrl + D + I : Open immediate window
Full Screen keyword
Shift + Alt + Enter :- To see full screen view
Scroll forward/backwards
Ctrl-Tab: Scroll forward through open windows
Ctrl-Shift-Tab: Scroll backwards through open windows
Attach the debugger to a process
Ctrl-Alt-P : This is insanely useful for debugging ASP.NET web sites without having to start the project in debug mode
Code/Designer windows
F7 : Show the code windows
Shift-F7 : Show the designer window
Bookmark keyword
Ctrl + B + T : Toggle code bookmark
Ctrl + B + E : Enable bookmark
Ctrl + B + P : Previous bookmark
Ctrl + B + N : Next bookmark
Ctrl + B + C : Clear bookmark
Open windows keyword
F4 :- Opens the Properties window
Ctrl + Alt + X :- Opens the Toolbar window
Ctrl + W + S :- Opens the Solution Explorer window
Ctrl + W + L :- Opens the Server Explorer window
Ctrl + W + C :- Opens the Class Viewer window
Ctrl + Shift + E :- Opens the Resource view window
Toggle character keyword
Ctrl + T : Toggle character
Snippet keyword
Ctrl + K + X - Insert Snippet
Intellisence keyword
Ctrl + Space - Intellisence
Line operations keyword
Ctrl + Enter - Insert a new line above the current line
Ctrl + x/Ctrl + L - Delete current line
Undo/Redo keyword
Ctrl-Z / Ctrl-Y: Undo typing / Redo typing
Navigate Forward/Backward
Ctrl + - : Navigate Backward
Ctrl + Shift + -: Navigate Forward
Friday, July 17, 2009
New Features of Visual Studio 2008 for .NET Professionals
New Features of Visual Studio 2008 for .NET Professionals
1. LINQ Support
2. Expression Blend Support
3. Windows Presentation Foundation
4. VS 2008 Multi-Targeting Support
5. AJAX support for ASP.NET
6. JavaScript Debugging Support
7. Nested Master Page Support
8. LINQ Intellisense and Javascript Intellisense support for silverlight applications
9. Organize Imports or Usings
10. Intellisense Filtering
11. Intellisense Box display position
12. Visual Studio 2008 Split View
13. HTML JavaScript warnings, not as errors
14. Debugging .NET Framework Library Source Code
15. In built Silverlight Library
16. Visual Studio LINQ Designer
17. Inbuilt C++ SDK
18. Multilingual User Interface Architecture - MUI
19. Microsoft Popfly Support
20. Free Tools and Resources
21. We can use for Commercial
1. LINQ Support
2. Expression Blend Support
3. Windows Presentation Foundation
4. VS 2008 Multi-Targeting Support
5. AJAX support for ASP.NET
6. JavaScript Debugging Support
7. Nested Master Page Support
8. LINQ Intellisense and Javascript Intellisense support for silverlight applications
9. Organize Imports or Usings
10. Intellisense Filtering
11. Intellisense Box display position
12. Visual Studio 2008 Split View
13. HTML JavaScript warnings, not as errors
14. Debugging .NET Framework Library Source Code
15. In built Silverlight Library
16. Visual Studio LINQ Designer
17. Inbuilt C++ SDK
18. Multilingual User Interface Architecture - MUI
19. Microsoft Popfly Support
20. Free Tools and Resources
21. We can use for Commercial
Wednesday, July 15, 2009
Features of CLR (Common Language Runtime)
Acronym of CLR is Common Language Runtime. It is heart of the .NET framework. It is the runtime that converts a MSIL code into the host machine language code, which is then executed appropriately. All Language have runtime and it is the responsibility of the runtime to take care of the code execution of the Program. For example, VB6 has MSVBVM60.DLL and Java has Java Virtual Machine etc. Similarly, .NET has CLR. Following are the responsibilities of CLR.
- Support for developer services (profiling, debugging)
In unmanaged code, when a program generates an exception, the kernel suspends the execution of the process and passes the exception information to the debugger by using the Win32 debugging API. The CLR debugging API provides the same functionality for managed code. When managed code generates an exception, the CLR debugging API suspends the execution of the process and passes the exception information to the debugger.
- Code Access Security(CAS)
The common language runtime (CLR) supports a security model called code access security for managed code. In this model, permissions are granted to assemblies based on the identity of the code.
A code group contains a permission set (one or more permissions). Code that performs a privileged action will perform a code access demand which will cause the common language runtime (CLR) to walk up the call stack and examine the permission set granted to the assembly of each method in the call stack. The code groups and permission sets are determined by the administrator of the machine who defines the security policy.
The security policy that determines the permissions granted to assemblies is defined in three different places:
1. Machine policy
2. User policy
3. Host policy
- Exception handling
You can handle following type of exceptions using /clr
1. Structured Exception Handling (SEH).
2. C++ exception handling.
3. CLR exceptions.
A CLR exception is any exception thrown by a managed type.
The System::Exception class provides many useful methods for processing CLR exceptions and is recommended as a base class for user-defined exception classes.
- Code management
The Microsoft .NET Framework has two main components.
1. Common Language Runtime (CLR)
2. .NET Framework class library.
The concept of code management is a fundamental principle of the CLR, and applications that the CLR manages are called "managed applications" or "managed code."
- Application memory isolation
Application Memory Isolation means that applications does not need to worry about allocation/de-allocation of memory, everything will be handled by the CLR. GC is the component in CLR which takes care of memory management.
- Access to metadata (enhanced type information)
- Managing memory for managed objects
One of the major productivity benefits that the common language runtime (CLR) offers developers of managed code are:
1. Garbage Collector (GC) makes sure any memory allocated on the managed heap is cleaned up after it is no longer needed.
2. It saved countless hours of developers while debugging difficult problems arising from memory leaks.
3. It also saves time in released memory, and double-freeing memory.
Garbage collection is a mechanism that allows the computer to detect when an object can no longer be accessed. It then automatically releases the memory used by that object (as well as calling a clean-up routine, called a "finalizer," which is written by the user). Some garbage collectors, like the one used by .NET, compact memory and therefore decrease your program's working set.
- Conversion of IL to native code.
- Interoperation between managed code, COM objects, and pre-existing DLL's (unmanaged code and data)
- Automation of object layout
- Verification of type safety
Type-safe code is code that accesses memory structures only in well-defined ways. For example, given a valid object reference, type-safe code can access memory at fixed offsets corresponding to actual field members. However, if the code accesses memory at arbitrary offsets inside or outside the range of memory that belongs to the object, then it is not type-safe. When assemblies are loaded in the CLR, prior to the MSIL being compiled using just-in-time (JIT) compilation, the runtime performs a verification phase that examines code to determine its type-safety. Code that successfully passes this verification is called verifiably type-safe code.
- Host Protection Attributes (HPAs)
The CLR provides a mechanism to annotate managed APIs that are part of the .NET Framework with certain attributes that may be of interest to a host of the CLR. Examples of such attributes include:
1. SharedState, which indicates whether the API exposes the ability to create or manage shared state (for example, static class fields).
2. Synchronization, which indicates whether the API exposes the ability to perform synchronization between threads.
3. ExternalProcessMgmt, which indicates whether the API exposes a way to control the host process.
Given these attributes, the host can specify a list of HPAs, such as the SharedState attribute, that should be disallowed in the hosted environment. In this case, the CLR denies attempts by user code to call APIs that are annotated by the HPAs in the prohibited list.
- Support for developer services (profiling, debugging)
In unmanaged code, when a program generates an exception, the kernel suspends the execution of the process and passes the exception information to the debugger by using the Win32 debugging API. The CLR debugging API provides the same functionality for managed code. When managed code generates an exception, the CLR debugging API suspends the execution of the process and passes the exception information to the debugger.
- Code Access Security(CAS)
The common language runtime (CLR) supports a security model called code access security for managed code. In this model, permissions are granted to assemblies based on the identity of the code.
A code group contains a permission set (one or more permissions). Code that performs a privileged action will perform a code access demand which will cause the common language runtime (CLR) to walk up the call stack and examine the permission set granted to the assembly of each method in the call stack. The code groups and permission sets are determined by the administrator of the machine who defines the security policy.
The security policy that determines the permissions granted to assemblies is defined in three different places:
1. Machine policy
2. User policy
3. Host policy
- Exception handling
You can handle following type of exceptions using /clr
1. Structured Exception Handling (SEH).
2. C++ exception handling.
3. CLR exceptions.
A CLR exception is any exception thrown by a managed type.
The System::Exception class provides many useful methods for processing CLR exceptions and is recommended as a base class for user-defined exception classes.
- Code management
The Microsoft .NET Framework has two main components.
1. Common Language Runtime (CLR)
2. .NET Framework class library.
The concept of code management is a fundamental principle of the CLR, and applications that the CLR manages are called "managed applications" or "managed code."
- Application memory isolation
Application Memory Isolation means that applications does not need to worry about allocation/de-allocation of memory, everything will be handled by the CLR. GC is the component in CLR which takes care of memory management.
- Access to metadata (enhanced type information)
- Managing memory for managed objects
One of the major productivity benefits that the common language runtime (CLR) offers developers of managed code are:
1. Garbage Collector (GC) makes sure any memory allocated on the managed heap is cleaned up after it is no longer needed.
2. It saved countless hours of developers while debugging difficult problems arising from memory leaks.
3. It also saves time in released memory, and double-freeing memory.
Garbage collection is a mechanism that allows the computer to detect when an object can no longer be accessed. It then automatically releases the memory used by that object (as well as calling a clean-up routine, called a "finalizer," which is written by the user). Some garbage collectors, like the one used by .NET, compact memory and therefore decrease your program's working set.
- Conversion of IL to native code.
- Interoperation between managed code, COM objects, and pre-existing DLL's (unmanaged code and data)
- Automation of object layout
- Verification of type safety
Type-safe code is code that accesses memory structures only in well-defined ways. For example, given a valid object reference, type-safe code can access memory at fixed offsets corresponding to actual field members. However, if the code accesses memory at arbitrary offsets inside or outside the range of memory that belongs to the object, then it is not type-safe. When assemblies are loaded in the CLR, prior to the MSIL being compiled using just-in-time (JIT) compilation, the runtime performs a verification phase that examines code to determine its type-safety. Code that successfully passes this verification is called verifiably type-safe code.
- Host Protection Attributes (HPAs)
The CLR provides a mechanism to annotate managed APIs that are part of the .NET Framework with certain attributes that may be of interest to a host of the CLR. Examples of such attributes include:
1. SharedState, which indicates whether the API exposes the ability to create or manage shared state (for example, static class fields).
2. Synchronization, which indicates whether the API exposes the ability to perform synchronization between threads.
3. ExternalProcessMgmt, which indicates whether the API exposes a way to control the host process.
Given these attributes, the host can specify a list of HPAs, such as the SharedState attribute, that should be disallowed in the hosted environment. In this case, the CLR denies attempts by user code to call APIs that are annotated by the HPAs in the prohibited list.
.Net Vs. Java - Similarities
Common Language Infrastructure (CLI - CLI is called the Common Language Runtime or CLR) and .NET languages such as C# and VB have many similarities to Sun's JVM and JAVA. Both are based on a virtual machine model that hides the details of the computer hardware on which programs run. MICROSOFT uses theirs Common Intermediate Language (MSIL - intermediate byte-code) , and SUN uses theirs Java bytecode. On DOTNET byte-code is always compiled before execution, either Just In Time (JIT) or in advance of execution using the ngen.exe utility. With JAVA the byte-code is either interpreted, compiled in advance, or compiled JIT.
Subscribe to:
Posts (Atom)