Project Report at BITS 0 1

1. Project Report at BITS 0 1 BITS 0 1 Pvt. Ltd. Company, Ahmedabad

2. Agenda • INTRODUCTION • VB.NET • ADO.NET • MY PROJECT

4. Microsoft Visual Basic.NET is a comprehensive introduction to Visual Basic programming using the Microsoft Visual Basic.NET software. It is also distributed as a component in the Microsoft Visual Studio .NET programming suite, which includes the: Microsoft Visual C# .NET Microsoft Visual C++.NET Microsoft Visual J#.NET compiler and Other .NET development tools. Visual Basic .NET is available in several different editors, Including Professional Edition Enterprise Developer Edition Enterprise Architect Edition Academic Edition

6. The Menu bar provides access to most of the commands that control the development environment. Menus and commands work as they do in all Windows based programs, and you can access them by using the keyboard or the mouse. The Menu bar is the Standard Toolbar, a collection of buttons that serve as shortcuts for executing commands and controlling the Visual Studio development environment. To activate a button on toolbar, click the button using the mouse. Along the bottom of the screen is the Windows taskbar. You can use the taskbar to switch between various Visual Studio .NET components and to activate other Windows-based programs.

7. The main tools that you will see in the Visual Studio development environment are: Solution Explore Properties Windows Windows Forms Designer Toolbox Output Window All forms files, including this one, have a tiny form icon next to them so that you can easily identify them. When you click the form file, Visual Studio highlights it is Solution Explorer, and some information about the file appears in the Properties window.

8. Use the Properties window to change the characteristics, or property settings, of the user interface elements on a form. A property settings is a quality of one of the objects in your user interface. You can change property settings by using the Properties window while you are creating your user interface, or you can add program code via Code Editor to change one or more property settings while your program settings while your program is running. The Properties window contains an Object drop-down list box that itemizes all the user interface elements on the form; the window also lists the property settings that can be changed for each object.

9. The Toolbox in the development environment. The Toolbox contains many of the controls that you will use to build Visual Basic applications. For Example, Label, Button, Picture Box, Listbox, etc., There are several different control collections in the Toolbox, and you can access them by clicking the tabs that you see within the toolbox. If You don’t see the Toolbox now, click Toolbox on the View Menu.

10. • Double-click the End button on the form. • After a few moments, the Code Editor appears in the center of the Visual Studio development environment. • Inside the Code Editor are program statements associated with the current form. • Program statements that are used together to perform some action are typically grouped in a programming construct called a procedure. • A common type of procedure is a Sub procedure, some times called a subroutine. Sub procedures include a Sub keyword in the first line and end with End Sub. • When a procedures is associated with a particular object and an event, it is called an event handler or an event procedure.

12. This diagram shows how ADO.NET is designed to work with a 3-tier or n-tier architecture. Client Tier: In our client tier, we use a DataSet that is entirely separate and independent from the middle tier. The client tier DataSet is a mirror image of the DataSet contained within the middle tier, and they communicate with each other through XML. Middle Tier: The middle tier DataSet communicates with the Data Providers to select, add, update, or delete information. The Data Providers establish a connection to the data tier whenever information needs to be managed. Data Tier : The data tier is where the data store is located, as a SQL Server or an OLE DB data provider.

13. The .NET Data Providers consist of a number of classes used to connect to a data source, execute commands, and return records. They form the data tier. The .NET Data Providers are sometimes called Managed Providers. There are two types of .NET Data Providers: The OLE DB Data Provider – To access any OLE DB provider including ODBC drivers for Oracle, Microsoft Access, Excel, FoxPro, Paradox, dBase, and any other native ODBC or OLE DB driver. It uses the System.Data.OleDb namespace. The SQL Server Data Provider– Specific to SQL Server 7.0 and greater. It is faster than the OLE DB provider because it doesn't have to go through the OLE DB layer – it communicates directly with SQL Server. It uses the System.Data.SqlClient namespace.

14. Within each managed provider are four components: The Connection, DataAdapter, Command, and DataReader objects. If you're using the SQL Server Data Provider, you use the SQLDataAdapter, SqlCommand, SQLDataReader, and SqlConnection form of these objects. For OLE DB Data providers, use the OleDbDataAdapter, OleDbCommand, OleDbDataReader, and OleDbConnection objects.

15. This opens a connection to the data source. You can use either the OleDbConnection or the SqlConnection object. For OLE DB Provider you use a Provider, Data Source, User ID,and Password in the connection string. This one connects to a Microsoft Access database: "Provider=Microsoft.Jet.OLEDB.4.0;Datasource=C:\Samples\Northwind.mdb;User ID=;Password=;" For SQL Provider you need the same arguments as for the OLE DB provider, but omit the Provider type (which is always SQLOLEDB). This one connects to an Oracle database: "Provider=MSDAORA;Data Source=MyOracleDB;User ID=myID;Password=myPWD;"