A.The dataset can be considered as an in-memory cache of the data retrieved from the database.So the dataset consites of the tables, relationship and constraints.
To insert, update or delete the data in the database we use the sqlcommand
Saturday, August 2, 2008
2.Why we need both server controls and html controls in asp.net. what is the difference between them?
A.HTML Server Controls:
This controls will follow similar syntax of html client side controls with the same set of properties (with runat="server" attribute). The purpose of this HTML Server controls is towards migration projects. And this HTML Server Controls doesn't support extensibility.
Web Server Controls:
These are very advanced controls if compared to HTML Controls. These controls overcome the extensibility problem which araises in HTML Server Controls. These controls are also called as Smart Controls, because these controls will produce HTML context based on reuested browser.
These Controls also supports data binding and xml based syntax with .net object model.
This controls will follow similar syntax of html client side controls with the same set of properties (with runat="server" attribute). The purpose of this HTML Server controls is towards migration projects. And this HTML Server Controls doesn't support extensibility.
Web Server Controls:
These are very advanced controls if compared to HTML Controls. These controls overcome the extensibility problem which araises in HTML Server Controls. These controls are also called as Smart Controls, because these controls will produce HTML context based on reuested browser.
These Controls also supports data binding and xml based syntax with .net object model.
3.Whats the diffrence between Custom Control and a User Control?
A.If none of the existing ASP.NET server controls meet the specific requirements of your applications, you can create either a Web user control or a Web custom control that encapsulates the functionality you need. The main difference between the two controls lies in ease of creation vs. ease of use at design time.
Web user controls are easy to make, but they can be less convenient to use in advanced scenarios. You develop Web user controls almost exactly the same way that you develop Web Forms pages. Like Web Forms, user controls can be created in the visual designer, they can be written with code separated from the HTML, and they can handle execution events. However, because Web user controls are compiled dynamically at run time they cannot be added to the Toolbox, and they are represented by a simple placeholder glyph when added to a page. This makes Web user controls harder to use if you are accustomed to full Visual Studio .NET design-time support, including the Properties window and Design view previews. Also, the only way to share the user control between applications is to put a separate copy in each application, which takes more maintenance if you make changes to the control.
Web custom controls are compiled code, which makes them easier to use but more difficult to create; Web custom controls must be authored in code. Once you have created the control, however, you can add it to the Toolbox and display it in a visual designer with full Properties window support and all the other design-time features of ASP.NET server controls. In addition, you can install a single copy of the Web custom control in the global assembly cache and share it between applications, which makes maintenance easier
Web user controls are easy to make, but they can be less convenient to use in advanced scenarios. You develop Web user controls almost exactly the same way that you develop Web Forms pages. Like Web Forms, user controls can be created in the visual designer, they can be written with code separated from the HTML, and they can handle execution events. However, because Web user controls are compiled dynamically at run time they cannot be added to the Toolbox, and they are represented by a simple placeholder glyph when added to a page. This makes Web user controls harder to use if you are accustomed to full Visual Studio .NET design-time support, including the Properties window and Design view previews. Also, the only way to share the user control between applications is to put a separate copy in each application, which takes more maintenance if you make changes to the control.
Web custom controls are compiled code, which makes them easier to use but more difficult to create; Web custom controls must be authored in code. Once you have created the control, however, you can add it to the Toolbox and display it in a visual designer with full Properties window support and all the other design-time features of ASP.NET server controls. In addition, you can install a single copy of the Web custom control in the global assembly cache and share it between applications, which makes maintenance easier
Wednesday, July 30, 2008
4.How to show graphs in ASP .net ?graphs will be based on the databse?
A.We can use
System.Drawing;
System.Drawing.Drawing2D;
name spaces for drawing graphs based on data from databases in web pages
System.Drawing;
System.Drawing.Drawing2D;
name spaces for drawing graphs based on data from databases in web pages
5.Explain the life cycle of an ASP .NET page?
A.Events in ASP.Net 1.1 & 2.0 :-
Application: BeginRequest
Application: PreAuthenticateRequest
Application: AuthenticateRequest
Application: PostAuthenticateRequest
Application: PreAuthorizeRequest
Application: AuthorizeRequest
Application: PostAuthorizeRequest
Application: PreResolveRequestCache
Application: ResolveRequestCache
Application: PostResolveRequestCache
Application: PreMapRequestHandler
Page: Construct
Application: PostMapRequestHandler
Application: PreAcquireRequestState
Application: AcquireRequestState
Application: PostAcquireRequestState
Application: PreRequestHandlerExecute
Page: AddParsedSubObject
Page: CreateControlCollection
Page: AddedControl
Page: AddParsedSubObject
Page: AddedControl
Page: ResolveAdapter
Page: DeterminePostBackMode
Page: PreInit
Control: ResolveAdapter
Control: Init
Control: TrackViewState
Page: Init
Page: TrackViewState
Page: InitComplete
Page: LoadPageStateFromPersistenceMedium
Control: LoadViewState
Page: EnsureChildControls
Page: CreateChildControls
Page: PreLoad
Page: Load
Control: DataBind
Control: Load
Page: EnsureChildControls
Page: LoadComplete
Page: EnsureChildControls
Page: PreRender
Control: EnsureChildControls
Control: PreRender
Page: PreRenderComplete
Page: SaveViewState
Control: SaveViewState
Page: SaveViewState
Control: SaveViewState
Page: SavePageStateToPersistenceMedium
Page: SaveStateComplete
Page: CreateHtmlTextWriter
Page: RenderControl
Page: Render
Page: RenderChildren
Control: RenderControl
Page: VerifyRenderingInServerForm
Page: CreateHtmlTextWriter
Control: Unload
Control: Dispose
Page: Unload
Page: Dispose
Application: PostRequestHandlerExecute
Application: PreReleaseRequestState
Application: ReleaseRequestState
Application: PostReleaseRequestState
Application: PreUpdateRequestCache
Application: UpdateRequestCache
Application: PostUpdateRequestCache
Application: EndRequest
Application: PreSendRequestHeaders
Application: PreSendRequestContent
Application: BeginRequest
Application: PreAuthenticateRequest
Application: AuthenticateRequest
Application: PostAuthenticateRequest
Application: PreAuthorizeRequest
Application: AuthorizeRequest
Application: PostAuthorizeRequest
Application: PreResolveRequestCache
Application: ResolveRequestCache
Application: PostResolveRequestCache
Application: PreMapRequestHandler
Page: Construct
Application: PostMapRequestHandler
Application: PreAcquireRequestState
Application: AcquireRequestState
Application: PostAcquireRequestState
Application: PreRequestHandlerExecute
Page: AddParsedSubObject
Page: CreateControlCollection
Page: AddedControl
Page: AddParsedSubObject
Page: AddedControl
Page: ResolveAdapter
Page: DeterminePostBackMode
Page: PreInit
Control: ResolveAdapter
Control: Init
Control: TrackViewState
Page: Init
Page: TrackViewState
Page: InitComplete
Page: LoadPageStateFromPersistenceMedium
Control: LoadViewState
Page: EnsureChildControls
Page: CreateChildControls
Page: PreLoad
Page: Load
Control: DataBind
Control: Load
Page: EnsureChildControls
Page: LoadComplete
Page: EnsureChildControls
Page: PreRender
Control: EnsureChildControls
Control: PreRender
Page: PreRenderComplete
Page: SaveViewState
Control: SaveViewState
Page: SaveViewState
Control: SaveViewState
Page: SavePageStateToPersistenceMedium
Page: SaveStateComplete
Page: CreateHtmlTextWriter
Page: RenderControl
Page: Render
Page: RenderChildren
Control: RenderControl
Page: VerifyRenderingInServerForm
Page: CreateHtmlTextWriter
Control: Unload
Control: Dispose
Page: Unload
Page: Dispose
Application: PostRequestHandlerExecute
Application: PreReleaseRequestState
Application: ReleaseRequestState
Application: PostReleaseRequestState
Application: PreUpdateRequestCache
Application: UpdateRequestCache
Application: PostUpdateRequestCache
Application: EndRequest
Application: PreSendRequestHeaders
Application: PreSendRequestContent
Tuesday, July 29, 2008
6.What is .net frame work?
A.Net framework is an environment provided on top of the OS which looks into
Memory management
Thread management
and provides
Language independence
Platform independence
It is defined by Microsoft as 'an environment for building, deploying and running web services and other applications. It consists of three main parts -- CLR, framework classes and ASP.Net'
.Net facilitates integration of code written for desktop applications with code written for web applications. It also facilitates creation of assemblies from code files written in different .net languages. It provides a common type system (CTS) for bringing data types of all languages on a common platform.
Memory management
Thread management
and provides
Language independence
Platform independence
It is defined by Microsoft as 'an environment for building, deploying and running web services and other applications. It consists of three main parts -- CLR, framework classes and ASP.Net'
.Net facilitates integration of code written for desktop applications with code written for web applications. It also facilitates creation of assemblies from code files written in different .net languages. It provides a common type system (CTS) for bringing data types of all languages on a common platform.
7.What is the maximum number of cookies that can be allowed to a web site?
A.20
Maximum number of cookies allowed is 300.
Maximum number of cookies allowed is 300.
Subscribe to:
Posts (Atom)