Skip to main content

Converting Between Types



All implicit conversions are allowed, if the destination type can accommodate all possible values of the source type. It’s called widening conversion. Like conversion from integer to double.

If the range or precision of the source type is more than the destination than it’s called narrowing conversion and requires explicit conversion.

System.Convert can be used to covert between the types that implement System.IConvertable interface.

Type.TryParse and type.TryParseExact are new in .NET.

Boxing and Unboxing:
Boxing converts a value type to a reference type and Unboxing converts a reference type to a value type.

Object A;
Int I=0, j=0;
A = (object)I;  //Boxing
j = (int)A;          //Unboxing

How to implement conversion in custom types:
             Override ToString() to provide conversion to string and Parse() to Create object from string.

Implement System.IConvertable interface to provide conversion through System.Convert. Use this technique to provide culture specific conversions.

Implement TypeConvert class to enable design-time conversion for use-in visual studio.

Conversion operator can be also used to convert implicitly or explicitly from one data type to another.

Public static implicit operator <Type A> (<Type B>)
OR
Public static explicit operator <Type A> (<Type B>)

Implementing IConvertible interface:
                                                Add IConvertible to the type definition and visual studio will automatically add 17 different methods including GetTypeCode, ChangeType, and ToType for each base method. Throw exception for those the conversion is invalid. After implementing IConvetible interface you can simply use it like:
            Type A; bool B;
            B = Convert.ToBoolean(A);

Comments

Popular posts from this blog

Culture Information and Localization in .NET

Namespace: System.Globalization CultureInfo Class:                 It provides information like the Format of numbers and dates, Culture’s Calendar, Culture’s language and sublanguage (if applicable), Country and region of the culture. The Basic use of CultureInfo class is shown here: • How string Comparisons are performed • How Number Comparison & Formats are performed • Date Comparison and Formats. • How resources are retrieved and used. Cultures are grouped into three categories: Invariant Culture : It’s Culture Insensitive. It can be used to build some trial application. It can be also used to build an application with hard-coded expiry date that ignores cultures. But using it for every comparison will be incorrect and inappropriate. Neutral Culture : English(en), Frensh(fr), and Spanish(sp). A neutral culture is related to language but it’s not related to specific regi...

Exposing .NET Components to COM

Namespace: System.Runtime.CompilerServices Building .NET Components for use by COM .Net framework generates COM Proxies known as COM Callable Wrapper (CCW) to be used by COM. No matter how many COM clients consume a given managed object, .Net runtime will create a single CCW. Write down you class and before building it, Select the configuration form the project properties named “ Register for COM interop ”. Hiding public .NET Classes from COM To hide a class or member just use the following attribute: [ComVisible(true/false)] . Deploying COM-Enabled Assemblies :       Check the following necessaries before creating CCW: 1.        All class have default constructor (no parameter). 2.        Exposed Types should be public . 3.        Any member exposed should be public . 4.        Abstract classes will not b...

ASP.NET Working with Web Configuration Files

Our sites are configured based on hierarchy of XML configuration files. Machine.config is top level configuration file located in Config: %WINDIR%\Microsoft.NET\Framework\ <version> \Config\machine.config These settings are framework level and common to all Windows, Console, Class Library, and Web application. Some of them could be overridden in Web.config while others are protected. Next in hierarchy is Root.config. It’s located in Config: %WINDIR%\Microsoft.NET\Framework\ <version> \Config\web.config It contains default web server settings. Optionally one can add at root of all websites a web.config to provide general settings related to all sites. Optionally to provide more control on settings one can add web.config in each web site and for each folder in that web site. Processing the Configuration files:                       ...