Monday, December 17, 2012
NameValueCollection In C#.NET
Description:
1. It’s a data structure that store data in Key(String) and Value(string) format.
2. It allows user to store multiple(duplicate) values for the same Key.
3. You can access data either via Key or via index.
4. It’s very similar to HashTable that also allow you to store data in Key and Value format.
5. When you add a value in the NameValueCollection , Its size grows automatically by relocation.
6. This class is situated in System.Collections.Specialized namespace.
7. Its performance is very poor than any other data structure like List, Dictionary or Hash Table so you must be very careful while choosing this data structure unless you tested it for performance.
Tuesday, November 27, 2012
Features of WCF
Service Orientation
One consequence of using WS standards is that WCF enables you to create service oriented applications. Service-oriented architecture (SOA) is the reliance on Web services to send and receive data. The services have the general advantage of being loosely-coupled instead of hard-coded from one application to another. A loosely-coupled relationship implies that any client created on any platform can connect to any service as long as the essential contracts are met.
Wednesday, June 13, 2012
Object Serialization in the .NET Framework
Introduction
Serialization can be defined as the process of storing the state of an object instance to a storage medium. During this process, the public and private fields of the object and the name of the class, including the assembly containing the class, is converted to a stream of bytes, which is then written to a data stream. When the object is subsequently deserialized, an exact clone of the original object is created.
When implementing a serialization mechanism in an object-oriented environment, you have to make a number of tradeoffs between ease of use and flexibility. The process can be automated to a large extent, provided you are given sufficient control over the process. For example, situations may arise where simple binary serialization is not sufficient, or there might be a specific reason to decide which fields in a class need to be serialized. The following sections examine the robust serialization mechanism provided with the .NET Framework and highlight a number of important features that allow you to customize the process to meet your needs.
Tuesday, June 12, 2012
Components of DOT.NET platform
Introduction
The basic components of .NET platform (framework) are:
.Net Applications (Win Forms,Web Applications,Web Services) | |
Data(ADO.Net) and XML Library | |
FrameWork Class Library(FCL) (IO,Streams,Sockets,Security,Reflection,UI) | |
Common Language Runtime(CLR) (Debugger,Type Checker,JITer,GC) | |
Operating System (Windows,Linux,UNIX,Macintosh,etc.,) |
Concept of Assembly in DOT.NET
What is a .Net Assembly?
The .NET assembly is the standard for components developed with the Microsoft.NET. Dot NET assemblies may or may not be executable, i.e., they might exist as the executable (.exe) file or dynamic link library (DLL) file. All the .NET assemblies contain the definition of types, versioning information for the type, meta-data, and manifest. The designers of .NET have worked a lot on the component (assembly) resolution.
There are two kind of assemblies in .NET;
- Private
- Shared/Public