Common Language Runtime (CTS)

Common language runtime (CLR) is runtime for all .Net languages.It’s responsilbe for executing & managing all code written in any language that targets the .Net plateform.It’s provides many core services for application, such as:

1.Garbage Collection (GC):Garbage collection is a CLR feature that automatically manages memory on behalf of an applicaton.You create objects and use it, but you don’t explicity release them.The CLR automatically release objects when they are no longer reference & in use.This eliminates memory leaks in application.

2.Code Verification:Code verification is a process that ensure all code is safe to run prior to execution.Code verification enforces type safty and therefore prevents code from performing illegal operation such as accessing invalid memory location

3.Code Access security:Code access security allows code to be granted or denied permissions to do things, depending on the security configuration gor a given machine.

Common Laguage Specification (CLS)

Common language specification is the sub-set of the Common type system(CTS).This is provide the cross language interoperability.

For Example:

VB .Net’s Integer is 32 bit which maps exactly to the IL Type int32

and C#  .Net’s int is 32 bit which maps exactly to the IL Type int32

    i.e              int (In C#)——––>  int32 (In IL) <–———- integer (In VB)

int (In C#) and Integer(In VB) both are exactly mapped to  int 32(In IL).

Common Type System(CTS):

Common type system defines the pre-define data types that are availbe in IL,so that all languages that target the .Net framwork will produce compile code that is ultimately based on the CTS.

For Example:

VB .Net’s Integer is 32 bit which maps exactly to the IL Type int32

and C#  .Net’s int is 32 bit which maps exactly to the IL Type int32

    i.e              int (In C#)——––>  int32 (In IL) <–———- integer (In VB)

        Difference between Users-define Function (UDF) and Store Procedure (SP)

Stored procedure

Definition of Store Procedure (SP): Stored procedure is a pre-compile of SQL statements (program or procedure) which is physically stored within a database. Stored procedure contains two type of parameter:-
1. In Put Parameters: - Input parameter means value (or values) passed to the store procedure
2. Out Put Parameters:- Out Put parameter means value(or values) take from the store procedure

The advantage of a stored procedure is that when it is run, in response to a user request, it is run directly by the database engine, which usually runs on a separate database server. As such, it has direct access to the data it needs to manipulate and only needs to send its results back to the user, doing away with the overhead of communicating large amounts of data back and forth.

User-defined function

Definition of User-defined function: A user-defined function is a routine that encapsulates useful logic for use in other queries. While views are limited to a single SELECT statement, user-defined functions can have multiple SELECT statements and provide more powerful logic than is possible with views.
 
User defined functions have 3 main categories
1. Scalar-valued function - returns a scalar value such as an integer or a timestamp. Can be used as column name in queries
2. Inline function - can contain a single SELECT statement.
3. Table-valued function - can contain any number of statements that populate the table variable to be returned. They become handy when you need to return a set of rows, but you can’t enclose the logic for getting this rowset in a single SELECT statement.
        Difference Between users define Function (UDF) and store procedure (SP)
1. UDF can be used in the SQL statements anywhere in the WHERE/HAVING/SELECT section where as Stored procedures cannot be.
2. UDFs that return tables (table values) can be treated as another row set. This can be used in JOINs with other tables.
3. Inline UDF’s can be though of as views that take parameters and can be used in JOINs and other Rowset operations.
4. Functions must always return a value (either a scalar value or a table). Stored procedures may return a scalar value, a table value or nothing at all.
5. Stored procedures are called independently, using the EXEC command, while functions are called from within another SQL statement.
6.Stored procedures have out put parameter but user-defined does not have to out put parameter

7. Of course there will be Syntax differences and here is a sample of that
Stored procedure
Code: SQL

  CREATE PROCEDURE dbo.StoredProcedure1
  /*
     (
      @parameter1 datatype = default value,
      @parameter2 datatype OUTPUT
     )
  */
  AS
     /* SET NOCOUNT ON */
     RETURN
  

User defined functions
Code: SQL

  CREATE FUNCTION dbo.Function1
     (
     /*
     @parameter1 datatype = default value,
     @parameter2 datatype
     */
     )
  RETURNS /* datatype */
  AS
     BEGIN
      /* sql statement … */
     RETURN /* value */
     END
  

ASP.NET Architecture 

ASP.NET Architecture follows below mentioned points:-   

ISAPI(aspnet_isapi.dll) : ISAPI is filter mechanism that filter the request and send to the actual worker process(aspnet_wp.exe).ASP.NET uses ISAPI to run on the Internet Information Server (IIS).Not only does IIS host ASP.NET but the ISAPI filter mechanism also allows both ASP and ASP.NET to coexist on the same IIS server. (IIS can direct a *.asp page to ASP and a *.aspx page to ASP.NET.)

Configuration : The configuration of ASP.NET is managed by information stored in XML-format in a configuration file (Web.Config).

Cache : The cache allows for improved performance of ASP.NET, as the most commonly requested pages would be served from the ASP.NET cache.

State management : State management services for ASP.NET are provided by the ASP.NET state service.

.NET Framework : The .NET Framework provides the Common Language Runtime (CLR), which compiles and manages the execution of ASP.NET code, and the class libraries, which offer prebuilt programmatic functionality for Web Forms, XML support, and exception handling.

ADO.NET : ADO.NET provides ASP.NET with connections to databases.

InProc Session State

InProc session mode indicates that session state is stored locally. This means that with InProc session state mode is actually stored as life objects in the AppDomain of the Web application. This is why the session state is lost when Aspnet_wp.exe (or W3wp.exe, for applications that run on Microsoft Internet Information Services [IIS] 6.0) or the AppDomain restarts.  

Session Data Is Lost When You Use ASP.NET InProc Session State Mode.

CAUSE

loadTOCNode(1, ’cause’);

Session state data is lost if the AppDomain or the Aspnet_wp.exe process (or the W3wp.exe process, for applications that run on Microsoft Internet Information Services [IIS] 6.0) is recycled. Generally, the AppDomain is restarted based on several factors:

RESOLUTION

loadTOCNode(1, ‘resolution’);

To work around this problem, you can use StateServer or SqlServer session state mode. ASP.NET provides these other approaches for storing session state data. In the StateServer and SqlServer modes, your session state is not stored in the AppDomain of the Web application.

OutProc Session State

In OutProc Session ,Sessin State is stored In the StateServer and SqlServer modes, your session state is not stored in the AppDomain of the Web application.

1.StateServer: Alternately, StateServer mode uses a stand-alone Microsoft Windows service to store session variables. Because this service is independent of Microsoft Internet Information Server (IIS), it can run on a separate server. You can use this mode for a load-balancing solution because multiple Web servers can share session variables. Although session variables are not lost if you restart IIS, performance is impacted when you cross process boundaries.
2.SqlServer: If you are greatly concerned about the persistence of session information, you can use SqlServer mode to leverage Microsoft SQL Server to ensure the highest level of reliability. SqlServer mode is similar to out-of-process mode, except that the session data is maintained in a SQL Server. SqlServer mode also enables you to utilize a state store that is located out of the IIS process and that can be located on the local computer or a remote server.

Welcome to WordPress.com. This is your first post. Edit or delete it and start blogging!