RAD Studio for Microsoft .NET - Embarcadero Technologies

More documents

Recommendations

Info

1 Deploying Database Applications for the RAD Studio for Microsoft .NET 1.1 Developing Database Applications with an existing table • View and test stored procedure parameters—specify values for Input or InputOutput parameters and execute the selected stored procedure • Migrate data—migrate table schema and data of one or more tables from one provider to another • Drag-and-drop schema objects onto forms to simplify application development—drag tables or stored procedures onto your application form for the .NET Framework to add connection components and automatically generate connection strings See Also ADO.NET Overview ( see page 14) AdoDbx.NET Data Types ( see page 11) The Data Explorer provides connectivity to several industry-standard databases, and can be extended to connect to other popular databases. The Data Explorer uses the ISQLDataSource interface to get a list of available providers, database connections, and schema objects that are supported by different providers. The list of available providers is persisted in the TAdoDbxDataSources.xml file, and the available connections are persisted in the TAdoDbxConnections.xml file. Once you have chosen a provider the ISQLMetadata interface is used to retrieve metadata and display a read-only tree view of database objects. The current implementation provides a list of tables, views, and stored procedures for all AdoDbx Client-supported databases. The Data Explorer lets you create new tables, alter or drop existing tables, migrate data from multiple tables from one provider to another, and copy and paste individual tables across ADO-supported databases. For all these operations, the Data Explorer calls into the ISQLSchemaCreate implementation of the provider. Additionally, the Data Explorer can be used to drag data from a data source to any RAD Studio project for the .NET framework. Dragging a table onto a form adds TAdoDbxConnection and TAdoDbxDataAdapter components to your application and automatically configures the TAdoDbxDataAdapter for the given table. Dragging a stored procedure onto a form adds TAdoDbxConnection and TAdoDbxCommand components to your application, and sets the CommandType property of the TAdoDbxCommand object to StoredProcedure. Using the Command Text Designer ( see page 127) Using the Connection Editor Designer ( see page 128) Using the Data Adapter Designer ( see page 128) Using the Data Adapter Preview ( see page 126) Using the Generate Dataset Designer ( see page 132) Migrating Data Between Databases ( see page 115) Creating Table Mappings ( see page 112) 1.1.8 Deploying Database Applications for the .NET Framework 24 When deploying database applications using RAD Studio, copy the necessary runtime assemblies and driver DLLs for deployment to a specified location. The following sections list the name of the assemblies and DLLs and the location of where each should reside. Note: We strongly encourage you to use ADO.NET and the AdoDbx Client Provider for .NET database applications. The Borland Data Provider is being deprecated.
1.1 Developing Database Applications with RAD Studio for Microsoft .NET Deploying Database Applications for the ADO.NET 2.0 Application Deployment Deploying by Updating machine.config The microsoft .net machine.config file must have an entry added for the provider. Locate machine.config below your Windows\Microsoft.net directory tree and add the following entry in the section: Deploying Without Updating machine.config An application can also deploy without updating the machine config by directly using the TAdoDbxProviderFactory class in the Borland.Data.AdoDbxClientProvider unit. Although this makes deployment easier, the TAdoDbxProviderFactory can only create ADO.NET 2.0 objects for the AdoDbxClient provider. If your application links with assemblies, the Borland.Data.AdoDbxClient.dll, and Borland.Data.DbxCommonDriver.dll assembly must be either copied to the same directory as your executable or registered in the GAC. If dbxconnections.ini and dbxdrivers.ini are used, they will have to also be deployed as well. If native dynalink drivers are being used, those drivers and their corresponding client libraries will need to be deployed. See Borland.Data.AdoDbxClientProvider.pas source file for information. BDP.NET Application Deployment Copy specific database runtime assemblies to the following location: Managed Assemblies Data Provider Location Borland.Data.Common.dll All GAC Borland.Data.Provider.dll All GAC Borland.Data.DB2.dll DB2 GAC Borland.Data.Interbase.dll Interbase GAC Borland.Data.Mssql.dll MS SQL/MSDE GAC Borland.Data.Oracle.dll Oracle GAC Borland.Data.Msacc.dll MS Access GAC Borland.Data.Sybase.dll Sybase GAC Note: If you are deploying a distributed database application that uses the BDP.NET Remoting components, such as DataHub, DataSync, RemoteConnection, and RemoteServer, you must install Borland.Data.DataSync.dll to the GAC. Copy unmanaged database driver DLLs to the following location: DLLs Data Provider Location bdpint20.dll Interbase search path bdpdb220.dll DB2 search path 25 1
Page 1: RAD Studio for Microsoft .NET Copyr
Page 4 and 5: iv RAD Studio for Microsoft .NET De
Page 6 and 7: vi RAD Studio for Microsoft .NET Cr
Page 8 and 9: 1 2 RAD Studio for Microsoft .NET 1
Page 10 and 11: 1 4 RAD Studio for Microsoft .NET 1
Page 12 and 13: 1 VCL for .NET Database Technologie
Page 14 and 15: 1 VCL for .NET Database Technologie
Page 16 and 17: 1 AdoDbx.NET Data Types RAD Studio
Page 18 and 19: 1 AdoDbx.NET Data Types RAD Studio
Page 20 and 21: 1 ADO.NET Overview RAD Studio for M
Page 22 and 23: 1 BDP Migration Overview RAD Studio
Page 24 and 25: 1 BDP Migration Overview RAD Studio
Page 26 and 27: 1 Blackfish SQL Overview RAD Studio
Page 28 and 29: 1 ADO.NET Component Designers RAD S
Page 32 and 33: 1 Data Providers for Microsoft .NET
Page 34 and 35: 1 Data Providers for Microsoft .NET
Page 36 and 37: 1 dbExpress Framework RAD Studio fo
Page 38 and 39: 1 Getting Started with InterBase Ex
Page 44 and 45: 1 Using COM Interop in Managed RAD
Page 46 and 47: 1 Using COM Interop in Managed RAD
Page 48 and 49: 1 Using DrInterop RAD Studio for Mi
Page 50 and 51: 1 Using Platform Invoke with Delphi
Page 58 and 59: 1 Virtual Library Interfaces RAD St
Page 60 and 61: 1 Code Visualization Overview RAD S
Page 62 and 63: 1 Using Rave Reports in RAD Studio
Page 64 and 65: 1 Changes Required Due to 64-bit .N
Page 66 and 67: 1 Language Issues in Porting VCL RA
Page 76 and 77: 1 Porting VCL Applications RAD Stud
Page 78 and 79: 1 VCL for .NET Overview RAD Studio
Page 80 and 81:
1 Porting Web Service Clients RAD S
Page 82 and 83:
1 Porting Web Service Clients RAD S
Page 84 and 85:
1 78 RAD Studio for Microsoft .NET
Page 86 and 87:
1 ASP.NET Overview RAD Studio for M
Page 88 and 89:
1 CodeGear DB Web Controls Overview
Page 90 and 91:
1 Using DB Web Controls in Master-D
Page 92 and 93:
1 DB Web Control Wizard Overview RA
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
1 Using XML Files with DB Web Contr
Page 100 and 101:
1 Deploying ASP.NET Applications RA
Page 102 and 103:
1 Working with WebDataLink Interfac
Page 104 and 105:
1 ASP.NET Web Services Overview RAD
Page 106 and 107:
1 Web Services Protocol Stack RAD S
Page 108 and 109:
1 ASP.NET Web Services Support RAD
Page 111 and 112:
2 RAD Studio for Microsoft .NET 2 P
Page 113 and 114:
2.1 Database Procedures RAD Studio
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
2.2 Interoperable Applications Proc
Page 147 and 148:
2.3 Modeling Procedures RAD Studio
Page 149 and 150:
2.3 Modeling Procedures RAD Studio
Page 151 and 152:
2.4 VCL for .NET Procedures RAD Stu
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
2.5 ASP.NET Procedures RAD Studio f
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
2.6 Web Services Procedures RAD Stu
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
3 RAD Studio for Microsoft .NET . .
Page 213 and 214:
3 RAD Studio for Microsoft .NET Con
Page 215 and 216:
3 RAD Studio for Microsoft .NET HTT
Page 217 and 218:
3 RAD Studio for Microsoft .NET Usi
show all

RAD Studio for Microsoft .NET - Embarcadero Technologies

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?