System.Object is the top .NET class that everything is derived from.
We use untrusted verification because web Services might use it, as well as non-windows applications. 

The advantages of Ado.Net  are-

  • ADO.NET does not depend on continuously live connections 
  • Database interactions are performed using data commands 
  • Data can be cached in datasets 
  • Datasets are independent of data sources 
  • Data is persisted as xml 
  • Schemas define data structures

We need to serialize the object, if you want to pass object from one computer/application domain to another. Process of converting complex objects into stream of bytes that can be persisted or transported. Namespace for serialization is System.Runtime.Serialization. The ISerializable interface allows you to make any class Serializable. .Net framework provides two serialization method-

  1. Binary Serialization 
  2. XML Serialization

Globalization is the process of creating an application that meets the needs of users from multiple cultures. It includes using the correct currency, date and time format, calendar, writing direction, sorting rules, and other issues. Accommodating these cultural differences in an application is called localization. Using classes of System.Globalization namespace, you can set applications current culture.
This can be achieved by using any of the following 3 approaches-

  • Detect and redirect.
  • Run-time adjustment.
  • Using Satellite assemblies.

Partial Assembly reference:  We can dynamically reference an assembly by providing only partial information, such as specifying only the assembly name. When you specify a partial assembly reference, the runtime looks for the assembly only in the application directory.
We can make partial references to an assembly in your code one of the following ways: 

  • Use a method such as System.Reflection.Assembly.Load and specify only a partial reference. The runtime checks for the assembly in the application directory.
  • Use the System.Reflection.Assembly.LoadWithPartialName method and specify only a partial reference. The runtime checks for the assembly in the application directory and in the global assembly cache.

Following steps are involved in creating shared assemblies:

  • Create your DLL/EXE source code
  • Generate unique assembly name using SN utility
  • Sign your DLL/EXE with the private key by modifying AssemblyInfo file
  • Compile your DLL/EXE
  • Place the resultant DLL/EXE in global assembly cache using AL utility

The Page_Load event handler in the page checks for IsPostBack property value, to ascertain whether the page is posted. The Page.IsPostBack gets a value indicating whether the page is being loaded in response to the client postback, or it is for the first time. The value of Page.IsPostBack is True, if the page is being loaded in response to the client postback; while its value is False, when the page is loaded for the first time. The Page.IsPostBack property facilitates execution of certain routine in Page_Load, only once (for e.g. in Page load, we need to set default value in controls, when page is loaded for the first time. On post back, we check for true value for IsPostback value and then invoke server-side code to update data).

There are four types of assemblies in .Net -
Static Assemblies: These are the .Net PE files that you create at compile time. 
Dynamic Assemblies: These are PE-formatted, in-memory assemblies that you dynamically create at runtime using the classes in the System.Reflection.Emit namespace.
Private Assemblies: These are static assemblies used by a specific application.
Public or Shared Assemblies: These are static assemblies that must have a unique shared name and can be used by any application.
An application uses a private assembly by referring to the assembly using a static path or through an XML based application configuration file. While the CLR does not enforce versioning policies-checking whether the correct version is used-for private assemblies, it ensures that an application uses the correct shared assemblies with which the application was built. Thus, an application uses a specific shared assembly by referring to the specific shared assembly, and the CLR ensures that the correct.

The default size of cache is doubles of your system RAM size.
i.e. if your RAM is of 128MB then the default cache size is 256MB.

PreviousDisplaying 5 of 6Next
1 2 3 4 5 6
Need Help? Contact Us.

Log in


Forgot password?


New User