The .NET framework comes with an entire namespace for handling e-mails, the System.Net.Mail namespace. In the following examples, we will use two classes from this namespace: The MailMessage class, for the actual e-mail, and the SmtpClient class, for sending the e-mail. 
As you may be aware, mails are sent through an SMTP server, and to send mails with the .NET framework, you will need access to an SMTP server. If you are testing things locally, the company that supplies your with Internet access, will usually have an SMTP server that you can use, and if you wish to use one of these examples on your actual website, the company that hosts your website will usually have an SMTP server that you can use. 

Every software has executable files (.exe). apart from the executable file, there are some Dynamic Link Libraries (DLL) & Library (LIB) files, which conyain the complicated code of some commonly used functions. These files come along with software. Any software package includes the executable file along with some DLLs & LIB files, which are necessary to run the application. In terms of .NET runtime, the process of packaging is called assembling. An assembly contains MSIL, metadata, & other files required to execute .NET program successfully.
In .NET Framework, assemblies play an important role. An assembly is an fundamental unit of deployment. Deployment is the process wherein an application installed on a machine. Assemblies can be created with the help of some development tools like Visual Studio or with the help of tools provided in .NET framework SDK. Assemblies can be make in form of .dll or .exe files using Visual Studio. When source code is compiled, the EXE/DLL, generated by default, is actually an assembly.

Every developer, especially beginners, will make errors whenever tries to create anything useful. Because of that, we need methods and tools for error handling. Fortunately, ASP.NET provides different ways to find, log or even try to correct errors when happened.
There are three different kinds of errors you can produce.

When you compile code that uses the .NET Framework library, you do not immediately create operating-system-specific native code. Instead, you compile your code into Common Intermediate Language (CIL) code. This code is not specific to any operating system (OS) and is not specific to C#. Other .NET languages — Visual Basic .NET, for example — also compile to this language as a first stage. This compilation step is carried out by VS or VCE when you develop C# applications. Obviously, more work is necessary to execute an application. That is the job of a just-in-time (JIT) compiler, which compiles CIL into native code that is specific to the OS and machine architecture being targeted. Only at this point can the OS execute the application. In the past, it was often necessary to compile your code into several applications, each of which targeted a specific operating system and CPU architecture. Typically, this was a form of optimization (to get code to run faster on an AMD chipset, for example), but at times it was critical (for applications to work in both Win9x and WinNT/2000 environments, for example). This is now unnecessary, because JIT compilers (as their name suggests) use CIL code, which is independent of the machine, operating system, and 
CPU. Several JIT compilers exist, each targeting a different architecture, and the appropriate one is used to create the native code required.

In general, a static assembly can consist of four elements:

  • The assembly manifest, which contains assembly metadata.
  • Type metadata.
  • Microsoft intermediate language (MSIL) code that implements the types.
  • A set of resources.

Only the assembly manifest is required, but either types or resources are needed to give the assembly any meaningful functionality.There are several ways to group these elements in an assembly like:

Sometimes, we required to show all items in Gridview or repeater but we do not want to implement paging. In this case, a scrolling grid is more applicable and enclosing the GridView in a Panel control or <div> tag with the overflow style applied ensures that the over-sized element is clipped and that scroll bars are displayed.
This solution works fine but whenever a postback occurs on page the div gets back to its original starting position. Here in this example, In order to maintain the scrolled position after postback I stored the div scroll value in hiddenfield using jquery and after postback we can get the scroll value from hiddenfield and set back to div to maintain the scroll position after asynchronous postback.

There are many types of collections in the .Net Framework. The most general types of them are under the "System.Collections" namespace. All of them have the following basic methods and properties to manipulate the stored data.-

Metadata is binary information describing program that is stored either in a common language runtime portable executable (PE) file or in memory. When code is compiled into a PE file, metadata is inserted into one portion of the file, while code is converted to Microsoft intermediate language (MSIL) and inserted into another portion of the file. Every type and member defined and referenced in a module or assembly is described within metadata. When code is executed, the runtime loads metadata into memory and references it to discover information about codes classes, members, inheritance, and so on.

Metadata describes every type and member defined in code in a language-neutral manner. Metadata stores the following information:
Description of the assembly

  • Identity (name, version, culture, public key).
  • The types that are exported.
  • Other assemblies that this assembly depends on.
  • Security permissions needed to run.
 Description of types
  • Name, visibility, base class, and interfaces implemented.
  • Members (methods, fields, properties, events, nested types).
  • Additional descriptive elements that modify types and members. applications can contain different file types. By default, some are supported and managed by ASP.NET, and others are supported and managed by the IIS server. Optionally, you can specify that all types should be handled by ASP.NET. Most of the ASP.NET file types can be automatically generated using the Add New Item menu item in Visual Studio.

Most of the server controls you find in the VWD Toolbox share some common behavior.
Part of this behavior includes the so-called properties that define the data a control can contain and expose.
Each server control has an ID to uniquely identify it in the page, a Runat attribute that is always set to Server to indicate the control should be processed on the server, and a ClientID that contains the client-side ID attribute that will be assigned to the element in the final HTML.

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

Log in


Forgot password?


New User