Directives for Asp.Net Web Pages

Directives are used to specify the settings used by the page or usercontrol compilers to process pages or usercontrol files
There are 11 types of directives1.@Page: This is used to define page specific attributes. It is used only in .aspx files2.@Control: This is used to define Control specific attributes. It is used only in .ascx files3.@Master: This is used to define masterpage specific attribute. It is used only in .master files4.@Import: This is used to import a namespace in to the current page or usercontrol5mailto:5.@Register: This is used to render usercontrols and custom server controls in to a current page or usercontrolmailto:6.@Assembly:: This is used to link a page or usercontrol in to current page or usercontrol8mailto:8.@Implements: This is used to implement a specific .Net framework Interface in to current page or usercontrol9mailto:9.@Outputcache: This is used to apply cache techniques in to the current page or usercontrol10.@MasterType: This defines a class or virtual path used to type the master property of a page11.@Previouspagetype: This is used to create a strongly typed reference to the source page from the target of a cross page posting.

Differences between Asp and Asp.net

ASP----------
1. Asp supports interpreted model2. In asp you must place all directives on the first line of a page with in the same delimiting block3. Asp uses only 2 scripting languages vb script and java script4. Asp has no inbuilt facility for Validation of controls. Developer has to write code for both client side and server side validation
ASP.NET------------
1. Asp.net supports compiled model2. In asp.net you can place directives at any place in .aspx file . But standard practice is to place them at the begining of the file3. Asp.net is not constrained to 2 languages. we can use any .net complaint languages like c# vb.net etc4. Asp.net inbuilt facility for validation of controls. There are a set of validation controls which are easy to implement.