 |
||
Language
/ DB Resource |
|
| Dot Net Code and Framework Concepts |
| The Common Language Runtime (CLR) :: |
| The Common Language Runtime is the heart of the .NET Framework. The core of the CLR is an execution engine that loads ,executes and manages code that has been compiled into an intermediate byte-code format called Microsoft Intermediate Language (MSIL and often refered as IL) .This code is not interpreted – it is compiled to a native binary code before execution by just-in-time compilers built into the CLR. |
| COM Componets :: |
| COM components implements one or more interfaces some of which are standard provided by the system and some of which are custom interfaces defined by the component developer.An interface defines a various methods that an application may invoke |
Services |
||||
| Software Development | ||||
 |
||||
| Web Development | ||||
|
||||
| Graphic Designing | ||||
|
||||
| Tools & Technologies | ||||
|
||||
| Multimedia Services | ||||
|
||||
| Web Marketing & SEO | ||||
|
||||
| Web Designing | ||||
|
||||
| Binding:: |
| The key to getting applications and components to work together is binding .COM offers two forms of binding : Early and Late |
| Early Binding : |
| The application uses a type library at compile time to work out how to link in to the methods in the component s interfaces . A type library can either come as a seperate file with extension .tlb,or as part of the DLL containing the component code. |
| Late Binding : |
| No connection is made between the application and its components at compile time. Instead the COM runtime searches through the component for the location of the required method when the application is actually run.This has two main disadvantages : its slower and its unreliable. |
| Process Versus Thread : |
The main difference between processes and threads is each process has its own address space where as thread don't. If a process creates multiple threads, all the threads will be contained in its address space. This is why they share resources so easily and interthread communication is so simple. |
| Difference Between Process and Thread : |
Threads share the address space of the process that created it; processes have their own address. Threads have direct access to the data segment of its process; processes have their own copy of the data segment of the parent process. Threads can directly communicate with other threads of its process; processes must use interprocess communication to communicate with sibling processes. Threads have almost no overhead; processes have considerable overhead. New threads are easily created; new processes require duplication of the parent process. Threads can exercise considerable control over threads of the same process; processes can only exercise control over child processes. |
| Advantages of Thread : |
Less system resources needed for context switching Increased throughput of an application No special mechanism required for communication between tasks Simplification of program structure |
| Server Error :: |
| Server Error in '/WebDirectory' Application.
Parser Error Parser Error Message: Could not load type 'WebDirectory.Global'. |
| Source Error: |
|
Line 1: <%@ Application Codebehind="Global.asax.cs" Inherits="WebDirectory.Global" %> Source File: c:\inetpub\wwwroot\WebDirectory\global.asax Line: 1 Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET Version:1.1.4322.573 |
| ADO Vs ADO.Net |
Traditional data access with ADO revolves around the fundamental data storage object - the Recordset.The technique used there is to create a connection to a data store using either an OLE-DB provider or an ODBC through OLE-DB driver(depending on the data store and the availability of the provider),then execure commands against it that return a Recordset object containing the appropriate data .This can be done using a Command Object ,or directly against the Connection object .Alternatively ,to insert or update data we simply execure a SQL statement or a stored procedure within the data store using the Connection object or Command object directly , without returning a Recordset object. The .NET data object model is based around one fundamental object -the DataSet . This replaces the Recordset from traditional ADO.It provides many new features that make complex data access technique more efficient ,while remaining as easy to use as the Recordset object.The main difference is that a DataSet object can hold more than one table (in other words more than one rowset )from the same data source, as well as the relationships between them. The DataSet object can also persist its contents, including more than one data table or rowset , directly as XML, and load from as XML document that contain structured data in the correct format.In fact,XML is the standard persistence format for data sets in .NET- bringing it more into line with the needs of disconnected and remote clients. |
| The DataSet Object in ADO.Net |
The DataSet object provides the basis for disconnected storage and manipulation of relational data. We fill it from a data store, work with it while disconnected from that data store , then reconnect and flush changes back to the data store if required. The main differences between a DataSet and the ADO Recordset are : The DataSet object can hold more than one table (more than one rowset in other words),as well as the relationships between them. The DataSet object automatically provides disconnected access to data. |