Creating and Sharing Reusable Components in ASP.NET 2.0
Prior to ASP.NET 2.0, if you were to reference a reusable component from your
ASP.NET application, you had to compile the assembly and place it in the bin
folder (or place it in the GAC) of the web application. But now with ASP.NET
2.0, creating a reusable component is very simple and straightforward. All you
need to do is create the component in a predefined subdirectory called
App_Code. Any component placed in this directory will be automatically compiled
at runtime into a single assembly. This assembly is automatically referenced
and will be available to all the pages in the site. Note that you should only
put components in the App_Code subdirectory.
More Related links
This includes explanation of code security, Principal object, declarative and
imperative security, role-based security, code access security and code group.
This includes caching mechanism in ASP.NET, its advantages and types.
Here you have details about exception handling and ways to handle exception in
ASP.NET. It also includes brief detail of Try/catch block, Error Events
and Custom Error Pages.
ASP.NET can also impersonate a specific account you specify in
web.config.........
The passing of the control from the child to the parent is called as
bubbling..........
ASP.NET runs inside the process of IIS due to which there are two authentication
layers which exist in the system.............
|
