HTTP Modules vs Global.asax Files

HTTP Modules vs Global.asax Files
You can implement much of the functionality of a Http modules in the application's Global.asax file, which enables you to respond to application events. However, modules have an advantage over the Global.asax file because they are encapsulated and can be created one time and used in many different applications. By adding them to the global assembly cache and registering them in the Machine.config file, you can reuse them across applications.

The advantage of using the Global.asax file is that you can handle other registered events such as Session_Start and Session_End. In addition, the Global.asax file enables you to instantiate global objects that are available throughout the application.

You should use a module whenever you must create code that depends on application events, and when the following conditions are true:

• You want to re-use the module in other applications.
• You want to avoid putting complex code in the Global.asax file.
• The module applies to all requests in the pipeline (IIS 7.0 Integrated mode only).

GAC - Global Assembly cache

GAC - Global Assembly cache
The global assembly cache stores assemblies specifically designated to be shared by several applications on the computer.

Worker Process and Application Pool in asp.net

Worker Process and Application Pool in asp.net
Worker Process:

Worker Process (w3wp.exe) runs the ASP.Net application in IIS. This process is responsible to manage all the request and response that are coming from client system.  All the ASP.Net functionality runs under the scope of worker process.  When a request comes to the server from a client worker process is responsible to generate the request and response. In a single word we can say worker process is the heart of ASP.NET Web Application which runs on IIS.

Application Pool:  

Application pool is the container of worker process.  Application pools is used to separate sets of IIS worker processes that share the same configuration.  Application pools enables a better security, reliability, and availability for any web application.  The worker process serves as the process boundary that separates each application pool so that when one worker process or application is having an issue or recycles, other applications or worker processes are not affected. This makes sure that a particular web application doesn't not impact other web application as they they are configured into different application pools.

Serialization and DeSerialization in C#

Serialization and DeSerialization in C#


Serialization is the process of converting an object into a stream of bytes in order to persist it to memory, a database, or a file. Its main purpose is to save the state of an object in order to be able to recreate it when needed. The reverse process is called deserialization.



The object is serialized to a stream, which carries not just the data, but information about the object's type, such as its version, culture, and assembly name. From that stream, it can be stored in a database, a file, or memory.

Serialization allows the developer to save the state of an object and recreate it as needed, providing storage of objects as well as data exchange. Through serialization, a developer can perform actions like sending the object to a remote application by means of a Web Service, passing an object from one domain to another, passing an object through a firewall as an XML string, or maintaining security or user-specific information across applications.

Binary Serialization

Binary serialization uses binary encoding to produce compact serialization for uses such as storage or socket-based network streams.

XML Serialization

XML serialization serializes the public fields and properties of an object, or the parameters and return values of methods, into an XML stream that conforms to a specific XML Schema definition language (XSD) document. XML serialization results in strongly typed classes with public properties and fields that are converted to XML.System.Xml.Serialization contains the classes necessary for serializing and deserializing XML.

SOAP Serialization

XML serialization can also be used to serialize objects into XML streams that conform to the SOAP specification. SOAP is a protocol based on XML, designed specifically to transport procedure calls using XML. As with regular XML serialization, attributes can be used to control the literal-style SOAP messages generated by an XML Web service.

Basic Serialization

The only requirement in basic serialization is that the object has the SerializableAttribute attribute applied. The NonSerializedAttribute can be used to keep specific fields from being serialized.

When you use basic serialization, the versioning of objects may create problems, in which case custom serialization may be preferable. Basic serialization is the easiest way to perform serialization, but it does not provide much control over the process.

Custom Serialization

In custom serialization, you can specify exactly which objects will be serialized and how it will be done. The class must be marked SerializableAttribute and implement theISerializable interface.

Html.TextBox vs Html.TextBoxFor in MVC

Html.TextBox vs Html.TextBoxFor in MVC

Html.TextBox and Html.DropDownList are not strongly typed and hence they doen't require a
strongly typed view. This means that we can hardcore whatever name we want.

On the other hand, Html.TextFor and Html.DropDownListFor are strongly typed and requires
a strongly typed view, and the name is inferred from the Lambda expression.

Whether we use Html.TextBox and Html.DropDownlist or Html.TextBoxFor and Html.DropDownListFor,
the end result is the same. they produce the same Html.

Nested List in C#

Nested List in C#

Consider there are two Class

 public class Person
    {
        public int Id { get; set; }
        public string FirstName { get; set; }
        public string LastName { get; set; }

        public List< Addresses > { get; set; }

    }

    public class Address
    {
        public string Line1 { get; set; }
        public string Line2 { get; set; }
        public string ZipCode { get; set; }
        public string City { get; set; }
        public string State { get; set; }
        public string Country { get; set; }
    }

Procedure used to add multiple class in the List
var personDetails = new List< Person >
                              {
                                  new Person
                                  {
                                      Id = 1, FirstName = "Arun",
                                      LastName = "Prakash",
                                      Addresses = new List< Address >
                                                      {
                                                          new Address{Line1 = "Hope College",Line2 = "Coimbatore"}
                                                 
                                                      }
                                  },
                                                                                                     
                                  new Person{
                                      Id = 2, FirstName = "Sanjay",
                                      LastName = "Ramasamy",
                                      Addresses = new List< Address >
                                                      {
                                                          new Address{Line1 = "Anna Salai",Line2= "Chennai"}
                                                     
                                                      }
                                  }
                              };

Html.RenderPartial vs Html.Partial, Html.RenderAction vs Html.Action

Html.RenderPartial vs Html.Partial, Html.RenderAction vs Html.Action 


@Html.Partial("Details")
@Html.Action("Index", "Home")

and

@{ Html.RenderPartial("Details"); }
@{ Html.RenderAction("Index", "Home"); }

Html.Partial returns a string, Html.RenderPartial calls Write internally, and returns void.

You can store the output of Html.Partial in a variable, or return it from a function. You cannot do this with Html.RenderPartial.

Html.RenderPartial -The result will be written to the Response stream during the execution.

The same is true for Html.Action and Html.RenderAction.