Install ado.net data services

The data provider supports Oracle client software version 8. The data provider supports both local and distributed transactions. OracleClient namespace and are contained in the System.

You must reference both the System. OracleClient namespace in your applications. Depending on the design and data source for your application, your choice of.

NET Framework data provider can improve the performance, capability, and integrity of your application. The following table discusses the advantages and limitations of each. NET Framework data provider. Unlike the other.

NET Framework data providers, it does not interact directly with a data source. Instead, it uses Entity SQL to communicate with the underlying data provider.

Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No. Any additional feedback? Note The. In this article. Uses the System. For data sources exposed by using ODBC. For Oracle data sources.

OracleClient namespace. The DataServiceCollection class is added to support two-way data binding. This collection class automatically tracks changes that are made on client-side objects. Changes are tracked for client-side objects that are created by using the ADO. A new feed customization feature is provided. Feed customization lets you shape and change the structure of Atom feeds that are produced by an ADO.

NET data service. When you change the structure of the Atom feed, third-party clients can consume feeds from an ADO. Clients are people who consume an Atom feed that has a custom format. The binary large object BLOB support is improved. This feature lets you upload and download binary objects from an application that is created by using the library.

This feature gives service authors more control over the network bandwidth and the time that are required to process requests. A new select query option enables query results to be projected into an arbitrary data type. This feature lets clients request a specific set of properties for an entity in a query. Reducing the number of properties in a query reduces the time and the network bandwidth that are required to process requests.

A new option lets you set the number of entities that a query returns. When the option contains the total number of entities that are in the entity set, the query returns a partial result. The request-processing pipeline is optimized. The optimization provides service authors more ability to control and customize at different stages of query processing.

The following file is available for download from the Microsoft Download Center: Update for the. For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:. It has been a while since I penned my last article, which I can only apologize for; see, I have been moving house, do not even have internet at my new house yet in fact, I have not even unpacked yet , so it has been slow progress with my trying to do a bit here and a bit there on the train with the trusty laptop.

Anyway, to cut a long story short, here is a new article. This article is not that complex, and will not give you any re-usable code in any shape, way, or form, but what it will hopefully do is give you a gentle introduction in how to get started with two of Microsoft's newer data access offerings:. Like I say, this is not an advanced article for people that may have used these two data access areas for some time; rather, it is a general overview of what can be done with these two different data access technologies and how you might go about doing some simple CRUD operations with them.

I should also point out that even though the attached demo code makes use of Silverlight, I have chosen, for the sake of brevity, to avoid complicating the reading experience by using the MVVM pattern. Even though I love that pattern, it is just not the point this article is trying to convey, so it's code-behind or XAML for this article's demo code, all the way. Please forgive me. And since both the ADO. In fact, just while we are talking about SQL, let me explain how you will need to setup your SQL Server database in order to run the demo app.

If you open up the attached solution, you will see a solution folder which holds several setup scripts that allow you to create the demo database:. After you have created the demo apps database, you must remember to change the connection string settings in the following two Web. Config to point to your SQL Server installation. The attached demo app is by no means a real world example, which may not please some people, but I did not want to create this huge overly complicated monster app when the basic CRUD principles could be demonstrated with a very easy database setup.

To this end, the demo app's database contains two simple tables; in fact, the demo code actually only uses one of these two tables, but you know what? It is also possible to delete, update, and insert new data using REST. NET Data Service,s you may not think so. Since WCF is used as the actual service implementation, all the core logic that fetches data from the database is run on an application server, so can be behind a firewall, which helps maintain that nice three levels of physical secure separation that we may all be used to.

I think this diagram explains it fairly well, where you can imagine the database is on one box, the Data Access Layer the ADO.

NET Data Service is on another physical box, and a client app such as Silverlight may be running on yet another different box basically, the client's PC. But before we get into that, we need to understand how to create an ADO. NET Data Service. So let's go through that, shall we? Is to define an Entity Model for the data. This is as easy well, for the demo app, it is anyway as creating a new Entity Model, and following the wizard through to completion, using your own SQL Server database connection string, and pointing to the WCFDataServicesDemoApp database you set up using the setup scripts provided and discussed above.

NET Data Service to expose the relational data as resources. Again, this is easy; all we need to do is add a new item as shown below:. Believe it or not, you are nearly there with creating a basic ADO.

NET Service. All you have to do is add the generic argument, which is the type of the EntityModel you created earlier, and decide which of your EntitySets you want to expose and what rights you want them to have. So for the demo app which is an insanely trivial example , this looks like this:.

Do not worry too much about the OnChangeAddresses method, I will get to that later. With this in place, we should be able to test this service out in the browser. We can see the ADO. NET Service is alive and kicking. Note the 2 x collection nodes in there: we have one for Addresses and one for Customers. Wonder what happens when we try one of these URLs. Shall we try one? See how we get a list of all the addresses:. Pretty cool, huh?

But what else can we do? Well, actually, we can do a whole lot more; for example, try some of these URLs:. So that shows you what is happening from the service point of view, but how do you go about using this as a client?

Luckily, there is a great Silverlight Client API to work with, which is what we shall talk about next. Right, so now it is time to see how we can actually consume some of the REST exposed resources in a client app. Obviously, as I am into Microsoft technologies, I will be using Silverlight. The demo app uses Silverlight 4. NET Data Services? NET Services installer I gave out a link at the start of the article.