Question 6 :
What is namespaces?
It is a logical group of related classes and interfaces and that can be used byany language targeting the .net framework.
Question 7 :
.NET framework overview
1. Has own class libraries. System is the main namespace and all other namespaces are subsets of this.
2. It has CLR(Common language runtime, Common type system, common language specification)
3. All the types are part of CTS and Object is the base class for all the types.
4. If a language said to be .net complaint, it should be compatible with CTS and CLS.
5. All the code compiled into an intermediate language by the .Net language compiler, which is nothing but an assembly.
6. During runtime, JIT of CLR picks the IL code and converts into PE machine code and from there it processes the request.
7. CTS, CLS, CLR
8. Garbage Collection
9. Dispose, finalize, suppress finalize, Idispose interface
10. Assemblies, Namespace: Assembly is a collection of class/namespaces. An assembly contains Manifest, Metadata, Resource files, IL code
11. Com interoperability, adding references, web references
12. Database connectivity and providers
1. Class modifiers: public, private, friend, protected, protected friend, mustinherit, NotInheritable
2. Method modifiers: public, private
8. Set/Get Property
1. Web Controls: Data grid (templates, sorting, paging, bound columns, unbound columns, data binding), Data list, repeater controls
2. HTML Controls
3. Code behind pages, system.web.ui.page base class
4. Web.config: App settings, identity (impersonate), authentication (windows, forms, anonymous, passport), authorization
6. Trace, Debug
7. Output cache
8. Session management
9. Application, Session
10. Global.asax httpapplication
11. User controls, custom controls, custom rendered controls (postback event, postdatachanged event) usercontrol is the base class
1. Command object (ExecuteNonquery, ExecuteReader, ExecuteXMLReader, ExecuteScalar)
2. DataAdapter object (Fill)
3. Dataset (collection of tables)
4. CommandBuiler object
5. Transaction Object
6. Isolation levels
Question 8 :
To test a Web Service you must create a windows application or web application to consume this service? It is True/False?
Question 9 :
How many classes can a single.NET DLL contain?
One or more
Question 10 :
What are good ADO.NET object(s) to replace the ADO Recordset object?
The differences includes
In ADO, the in-memory representation of data is the Recordset.
In ADO.net, it is the dataset
A recordset looks like a single table in ADO
In contrast, a dataset is a collection of one or more tables in ADO.net
ADO is designed primarily for connected access
ADO.net the disconnected access to the database is used
In ADO you communicate with the database by making calls to an OLE DB provider.
In ADO.NET you communicate with the database through a data adapter (an OleDbDataAdapter, SqlDataAdapter, OdbcDataAdapter, or OracleDataAdapter object), which makes calls to an OLE DB provider or the APIs provided by the underlying data source.
In ADO you cant update the database from the recordset. ADO.NET the data adapter allows you to control how the changes to the dataset are transmitted to the database.