1. ASP.NET Introduction 2. Comp of .Net Framework 3.5 3. Sys.Req for VS 2008 4. ASP.NET Envrmnt Setup 5. VS2010 Ultimate Sys.Req 6. Installing VS 2010 7. VS 2012 Sys.Req 8. Installing VS Exp 2012 9. Start the VS 2008 10. Application Life Cycle 11. Page Life Cycle 12. Page Life Cycle Events 13. ASP.NET Example 14. Event Handling 15. Default Events 16. Server Side 17. Request Object 18. Response Object 19. Server Controls 20. Server Controls Properties 21. Server Controls Methods 22. HTML Server Controls 23. Client Side 24. ASP.NET Basic Controls 25. TextBox Control 26. CheckBox Controls 27. RadioButton Controls 28. ListBox Control 29. HyperLink Control 30. Image Control 31. BulletedList Control 32. ASP.NET Directives 33. Implements Directive 34. Master Type Directive 35. Page Directive 36. PreviousPage Type 37. Managing State 38. Control State 39. Cookies 40. Query Strings 41. Server-Side State 42. Session State 43. Validation Controls 44. Required FieldValidator 45. Range Validator 46. Compare Validator 47. RegularExpressionValidator 48. Custom Validator 49. Validation Summary 50. Data Source Control 51. AdRotator Control 52. Calendar Control 53. Calendar Control Example 54. Panel Control 55. Panel Control Example 56. Multi Views Control 57. MultiView & View controls 58. MultiView Control Example 59. FileUpload Control 60. FileUpload Control Eg 61. AJAX Control 62. UpdatePanel control 63. UpdateProgress Control 64. Custom Controls 65. Custom Control Eg 66. Personalization 67. Create Simple Profile 68. ADO.NET 69. ADO.NET Objects 70. DataTable 71. DataRow 72. DataColumn 73. Object Example 74. Error Handling 75. Tracing Errors 76. Debugger 77. Security 78. Authentication 79. Authorization 80. LINQ 81. LINQ Query Operators 82. LINQ Example 83. Caching 84. Data Caching 85. Output Caching 86. Object Caching 87. Web Services 88. Create Web Services Eg 89. Web & Machine.config 90. Settings Schema 91. ASP.NET Deployment 92. XCopy Deployment 93. Web Setup Project 94. ASP Interview Part 1 95. ASP Interview Part 2 96. ASP Interview Part 3 97. ASP Interview Part 4 98. ASP Interview Part 5 99. ASP Interview Part 6
Pr.Pg Next Pg

@Implements Directive tutorials

  • The Implements directive is used in page (.aspx) and user control (.ascx) files or associated code-behind files. It specifies a COM+ interface that the current page implements. This allows a page or user control to declare the interface's events, methods, and properties.



The syntax of Implements Directive is:

<%@ Implements interface="ValidInterfaceName" %>

  • The attributes of Implements directive is:

Interface: The interface to be implemented on the page or user control.


@Import Directive

  • The @Import directive imports a namespace into a page, user control, or application, making all the classes and namespaces of the imported namespace available. It is analogous to the using statement in C# and the Imports statement in VB.NET. Imported namespaces can either be part of the .NET Framework Class Library or custom.

  • If the Import directive is contained in global.asax, then it applies to the entire application. If it is in a page (.aspx) or user control (.ascx) file, then it only applies to that page or user control.

  • Each Import directive can have only a single namespace attribute. If you need to import multiple namespaces, use multiple Import directives.



The syntax of Import directive is:

<%@ Import namespace="value" %>

  • The attributes of import directive is:

namespace: The fully qualified name of the namespace to import. This can include any of the namespaces included in the .NET Framework or a custom namespace.

  • Example: The following code example imports the .NET Framework base-class namespace System.Net and the user-defined namespace Grocery.

<%@ Import Namespace="System.Net" %>

<%@ Import Namespace="Grocery" %>

@ Master Directive

  • Defines master page–specific (.master file) attributes that are used by the ASP.NET page parser and compiler.

  • Some of the attributes of the master page directive is :- Code File, Debug, Language, Inherits, EnableView State, MasterPageFile, Src.



The syntax of master directive is.

<%@ Master attribute="value" [attribute="value"...] %>


<%@ Master Language="C#" %>


  • The following table shows the list of attributes and description of master directive.





Indicates whether simple event handlers can be defined for specific life cycle stages using the syntax Page without any explicit hookup or event signature

True if event auto-wiring is enabled; otherwise, false. The default is true.


Specifies the class name for the class that is automatically generated from the markup and compiled when the master page is processed


Specifies the name of a separate file that contains a partial class with the event handlers and other master page–specific code


Specifies whether to compile an ASP.NET master page at run time, Options are Always to always compile the page; Auto, if ASP.NET is to avoid compiling the page, if possible; and Never, to never compile the page or control. The default is Always.


Provides a string containing compiler options to use to compile the page


Indicates whether to compile the master page with debug symbols. true, to compile with debug symbols; otherwise, false.


Provides a text description of the master page. This value is ignored by the ASP.NET parser.


Indicates whether the appearance of the master page and of controls on the master page can be modified, if a theme is applied. true if a theme can be applied; otherwise, false. The default is true.


Indicates whether view state is maintained across page requests. true to maintain view state; otherwise, false. The default is true.


If language is VB, tells compiler to use Option Explicit mode. Default is false.


Specifies a code-behind class for the page to inherit, This can be any class derived from the MasterPage class.


Specifies the language used when compiling all inline rendering (<% %> and <%= %>) and code declaration blocks within the page.


Determines whether the runtime should generate pragmas in the generated code


Specifies the .master file that acts as a master page for a master page 


Specifies the source file name of the code-behind class to dynamically compile when the page is requested


Specifies whether to compile the page using the Visual Basic Option Strict mode.true if Option Strict is enabled; otherwise, false The default is false.


Indicates the compiler warning level at which you want the compiler to treat warnings as errors, thus aborting compilation of the control. Possible warning levels are 0 through 4.


Pr.Pg border                                              Next Pg