This HTML5 document contains 56 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

PrefixNamespace IRI
n12http://vos.openlinksw.com/wiki/main/VOS/VirtUsingMsAdoNetDataServicesWithVirtuoso/VirtAdoNetDataServices_10.
n18http://vos.openlinksw.com/wiki/main/VOS/VirtUsingMsAdoNetDataServicesWithVirtuoso/VirtAdoNetDataServices_3.
n16http://vos.openlinksw.com/wiki/main/VOS/VirtUsingMsAdoNetDataServicesWithVirtuoso/VirtAdoNetDataServices_5.
n27http://rdfs.org/sioc/services#
dchttp://purl.org/dc/elements/1.1/
n24http://vos.openlinksw.com/wiki/main/VOS/VirtUsingMsAdoNetDataServicesWithVirtuoso/VirtAdoNetDataGridApp9.
n35http://vos.openlinksw.com/wiki/main/VOS/VirtUsingMsAdoNetDataServicesWithVirtuoso/VirtAdoNetDataServices_8.
n11http://vos.openlinksw.com/wiki/main/VOS/VirtUsingMsAdoNetDataServicesWithVirtuoso/VirtAdoNetDataServices_1.
n9http://vos.openlinksw.com/dataspace/owiki#
n7http://vos.openlinksw.com/dataspace/%28NULL%29/wiki/VOS/
n38http://vos.openlinksw.com/wiki/main/VOS/VirtUsingMsAdoNetDataServicesWithVirtuoso/VirtAdoNetDataServices_15.
n2http://vos.openlinksw.com/dataspace/owiki/wiki/VOS/
dctermshttp://purl.org/dc/terms/
n26http://vos.openlinksw.com/dataspace/services/wiki/
n39http://vos.openlinksw.com/wiki/main/VOS/VirtUsingMsAdoNetDataServicesWithVirtuoso/VirtAdoNetDataServices_16.
rdfshttp://www.w3.org/2000/01/rdf-schema#
n4http://vos.openlinksw.com/wiki/main/VOS/VirtUsingMsAdoNetDataServicesWithVirtuoso/VirtAdoNetDataServices_11.
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n8http://vos.openlinksw.com/wiki/main/VOS/VirtUsingMsAdoNetDataServicesWithVirtuoso/VirtAdoNetDataServices_12.
atomhttp://atomowl.org/ontologies/atomrdf#
n13http://vos.openlinksw.com/wiki/main/VOS/VirtUsingMsAdoNetDataServicesWithVirtuoso/VirtAdoNetDataServices_6.
n28http://vos.openlinksw.com/dataspace/dav#
xsdhhttp://www.w3.org/2001/XMLSchema#
siochttp://rdfs.org/sioc/ns#
n33http://vos.openlinksw.com/wiki/main/VOS/VirtUsingMsAdoNetDataServicesWithVirtuoso/VirtProviderAddDSNErr.
n31http://vos.openlinksw.com/dataspace/owiki/wiki/VOS/VirtUsingMsAdoNetDataServicesWithVirtuoso/sioc.
n25http://vos.openlinksw.com/wiki/main/VOS/VirtUsingMsAdoNetDataServicesWithVirtuoso/VirtAdoNetDataGridApp7.
n32http://vos.openlinksw.com/dataspace/person/owiki#
n15http://vos.openlinksw.com/wiki/main/VOS/VirtUsingMsAdoNetDataServicesWithVirtuoso/VirtAdoNetDataServices_4.
n19http://vos.openlinksw.com/wiki/main/VOS/VirtUsingMsAdoNetDataServicesWithVirtuoso/VirtAdoNetDataServices_17.
oplhttp://www.openlinksw.com/schema/attribution#
n40http://vos.openlinksw.com/wiki/main/VOS/VirtUsingMsAdoNetDataServicesWithVirtuoso/VirtAdoNetDataServices_13.
n5http://vos.openlinksw.com/dataspace/person/dav#
n23http://vos.openlinksw.com/wiki/main/VOS/VirtUsingMsAdoNetDataServicesWithVirtuoso/VirtAdoNetDataGridApp8.
n17http://vos.openlinksw.com/wiki/main/VOS/VirtUsingMsAdoNetDataServicesWithVirtuoso/VirtAdoNetDataServices_2.
n36http://vos.openlinksw.com/wiki/main/VOS/VirtUsingMsAdoNetDataServicesWithVirtuoso/VirtAdoNetDataServices_9.
foafhttp://xmlns.com/foaf/0.1/
n20http://vos.openlinksw.com/wiki/main/VOS/VirtUsingMsAdoNetDataServicesWithVirtuoso/VirtAdoNetDataServices_18.
siocthttp://rdfs.org/sioc/types#
n14http://vos.openlinksw.com/wiki/main/VOS/VirtUsingMsAdoNetDataServicesWithVirtuoso/VirtAdoNetDataServices_7.
n22http://vos.openlinksw.com/dataspace/owiki/wiki/
n41http://vos.openlinksw.com/wiki/main/VOS/VirtUsingMsAdoNetDataServicesWithVirtuoso/VirtAdoNetDataServices_14.
Subject Item
n5:this
foaf:made
n2:VirtUsingMsAdoNetDataServicesWithVirtuoso
Subject Item
n28:this
sioc:creator_of
n2:VirtUsingMsAdoNetDataServicesWithVirtuoso
Subject Item
n26:item
n27:services_of
n2:VirtUsingMsAdoNetDataServicesWithVirtuoso
Subject Item
n9:this
sioc:creator_of
n2:VirtUsingMsAdoNetDataServicesWithVirtuoso
Subject Item
n22:VOS
sioc:container_of
n2:VirtUsingMsAdoNetDataServicesWithVirtuoso
atom:entry
n2:VirtUsingMsAdoNetDataServicesWithVirtuoso
atom:contains
n2:VirtUsingMsAdoNetDataServicesWithVirtuoso
Subject Item
n2:VirtUsingMsAdoNetDataServicesWithVirtuoso
rdf:type
sioct:Comment atom:Entry
dcterms:created
2017-06-13T05:38:43.312351
dcterms:modified
2017-06-29T07:41:48.538521
rdfs:label
VirtUsingMsAdoNetDataServicesWithVirtuoso
foaf:maker
n5:this n32:this
dc:title
VirtUsingMsAdoNetDataServicesWithVirtuoso
opl:isDescribedUsing
n31:rdf
sioc:has_creator
n28:this n9:this
sioc:attachment
n4:png n8:png n11:png n12:png n13:png n14:png n15:png n16:png n17:png n18:png n19:png n20:png n23:png n24:png n25:png n33:png n35:png n36:png n38:png n39:png n40:png n41:png
sioc:content
%VOSWARNING% %META:TOPICPARENT{name="VirtAdoNet35Provider"}% ---+ Using Microsoft ADO.Net Data Services with Virtuoso %TOC% ---++ Introduction: The goal of Microsoft ADO.NET Data Services is to enable applications to expose data as a data service that can be consumed by web clients within corporate networks and across the internet. A data service is reachable via regular HTTP requests, using standard HTTP verbs such as GET, POST, PUT and DELETE to perform CRUD operations against the service. The payload format used by the service is controllable by the application, but all options are simple, open formats such as JSON and Atom/APP. The use of web-friendly technologies make ADO.NET Data Services ideal as a data back-end for AJAX-style applications, Rich Interactive Applications and other applications that need to operate against data that is stored across the web. ---++ Getting Started: Creating Data Services ---+++ Pre-requisites In order to create a data service using ADO.NET Data Services in your own environment you will need: 1 Microsoft Visual Studio 2008 SP1, the ADO.NET Entity Framework runtime and associated tools are included in Visual Studio 2008 SP1. 1 A running Virtuoso Universal Server instance. ---+++ Selecting a Data Source The ADO.NET Data Service server framework is comprised of two halves. The top-half is the runtime itself; this part is ?fixed?, and it implements URI translation, the Atom/JSON wire formats, the interaction protocol, etc. This is what makes an ADO.NET Data Service look like an ADO.NET Data Service. The bottom half is the data-access layer and is pluggable. Communication between layers happens in terms of the IQueryable interface plus a set of conventions to map CLR graphs into the URI/payload patterns of ADO.NET Data Services. The first step in creating an ADO.NET Data Service is to determine the data source that is to be exposed as a set of REST-based endpoints (i.e., select or create a data access layer). For relational data stored in Microsoft SQL Server or other 3rd Party databases, ADO.NET Data Services currently enables easily exposing a conceptual model created using the ADO.NET Entity Framework (EF). For all other data sources (XML document, web service, application logic layer, etc) or to use additional database access technologies (ex. LINQ to SQL), a mechanism is provided which enables any data source, as per the plug-in model described above, to be exposed as an ADO.NET Data Service. To create a data service which exposes a relational database through an Entity Framework conceptual model see ?Creating a Data Service using the ADO.NET Entity Framework?. To create a data service which exposes another data source see ?Creating a Data Service from any Data Source?. ---+++ Creating a Data Service using the ADO.NET Entity Framework ADO.NET Data Services are a specialized form of Windows Communication Foundation services, and thus can be hosted in various environments. The below example will create an ADO.NET Data Service which is hosted inside an ASP.NET site. In order to create a data service, you must first create a web project; you will then need to establish a connection with the database that will be exposed by the service, and then create the data service itself within the web application. Below is a step-by-step description of this process. The following steps can be used for creating a Data Service using the Virtuoso ADO.Net Provider for accessing the sample Northwind Demo database: 1 Launch the Visual Studio 2008 SP1 IDE. %BR%%BR%<img src="%ATTACHURLPATH%/VirtAdoNetDataServices_1.png" style="wikiautogen"/>%BR%%BR% 1 Create a <b>Web Application</b> project by going to the <b>File</b> menu in Visual Studio and choosing <b>New Project</b>. %BR%%BR% 1 When the New Project window appears, choose either <b>Visual Basic</b> or <b>Visual C#</b> as the programming language.%BR%%BR% 1 Within the language category click on <b>Web</b>, and select <b>ASP.NET Web Application</b> from the right-hand panel. %BR%%BR% 1 Choose a name for the project, for example <b><nop>VirtuosoDataService</b>, and click <b>OK</b>. %BR%%BR%<img src="%ATTACHURLPATH%/VirtAdoNetDataServices_2.png" style="wikiautogen"/>%BR%%BR% 1 This will create a new project called <b><nop>VirtuosoDataService</b>. %BR%%BR%<img src="%ATTACHURLPATH%/VirtAdoNetDataServices_3.png" style="wikiautogen"/>%BR%%BR% 1 Right click on the <b><nop>VirtuosoDataService</b> project name of the <b>Solution Explorer</b> pane, then select the <b>Add</b> -> <b>New Item</b> menu options. %BR%%BR%<img src="%ATTACHURLPATH%/VirtAdoNetDataServices_4.png" style="wikiautogen"/>%BR%%BR% 1 The <b>Add New Item</b> dialog will appear, choose the <b>ADO.NET Entity Data Model</b> template, give it the name <b>Virtuoso.edmx</b> and click <b>Add</b> to start the creation of the ADO.Net Entity Data Model. %BR%%BR%<img src="%ATTACHURLPATH%/VirtAdoNetDataServices_5.png" style="wikiautogen"/>%BR%%BR% 1 In the <b>Entity Data Model Wizard</b> dialog <b>Choose Model Contents</b> page select the <b>Generate from Database</b> model type and click <b>Next</b>. %BR%%BR%<img src="%ATTACHURLPATH%/VirtAdoNetDataServices_6.png" style="wikiautogen"/>%BR%%BR% 1 In the <b>Entity Data Model Wizard</b> dialog <b>Choose your Data Connection</b> page select the <b>New Connection</b> button %BR%%BR%<img src="%ATTACHURLPATH%/VirtAdoNetDataServices_7.png" style="wikiautogen"/>%BR%%BR% 1 In the <b>Choose Data Source</b>dialog, select the <b>OpenLink Virtuoso Data Source</b> from the list displayed and click <b>Continue</b>. %BR%%BR%<img src="%ATTACHURLPATH%/VirtAdoNetDataServices_8.png" style="wikiautogen"/>%BR%%BR% 1 In the <b>Add Connection</b> dialog, specify the <b>hostname</b>, <b>portno</b>, <b>username</b>, and <b>password</b> for the target Virtuoso Server and check the <b>Save Password</b> check box. %BR%%BR%<img src="%ATTACHURLPATH%/VirtAdoNetDataGridApp7.png" style="wikiautogen"/>%BR%%BR% 1 Select the <b>Select Database From List</b> radio button and choose <b>Demo</b> from the drop down list, assuming the Virtuoso Demo Database is installed. %BR%%BR%<img src="%ATTACHURLPATH%/VirtAdoNetDataGridApp8.png" style="wikiautogen"/>%BR%%BR% 1 Click the <b>Test Connection</b> button to verify the connection is successful and then click <b>OK</b> to add the connection.%BR% %BR%%BR%<img src="%ATTACHURLPATH%/VirtAdoNetDataGridApp9.png" style="wikiautogen"/>%BR%%BR% 1 Set the <b>entity connect string</b> name to <b>VirtuosoDemoEntities</b> (note this name as it is required in step 17 below) and click <b>Next</b>. %BR%%BR%<img src="%ATTACHURLPATH%/VirtAdoNetDataServices_12.png" style="wikiautogen"/>%BR%%BR% 1 In the <b>Choose your Database Objects</b> page select the <b>Tables</b> check box to select all tables in the Demo database for addition to the Entity Data Model, set the <b>Model Namespace</b> to <b>VirtuosoDemoModel</b> and click <b>Finish</b>. %BR%%BR%<img src="%ATTACHURLPATH%/VirtAdoNetDataServices_13.png" style="wikiautogen"/>%BR%%BR% 1 The <b>Virtuoso.edmx</b> EDM will be created with the tables and relationships displayed in the Visual Studio IDE %BR%%BR%<img src="%ATTACHURLPATH%/VirtAdoNetDataServices_14.png" style="wikiautogen"/>%BR%%BR% 1 Right click on the <b><nop>VirtuosoDataService</b> project name of the <b>Solution Explorer</b> pane, then select the <b>Add</b> -> <b>New Item</b> menu options. %BR%%BR%<img src="%ATTACHURLPATH%/VirtAdoNetDataServices_4.png" style="wikiautogen"/>%BR%%BR% 1 The <b>Add New Item</b> dialog will appear, choose the <b>ADO.NET Data Service</b> template, give it the name <b>Virtuoso.svc</b> and click <b>Add</b> to create the ADO.Net Data Service. %BR%%BR%<img src="%ATTACHURLPATH%/VirtAdoNetDataServices_15.png" style="wikiautogen"/>%BR%%BR% 1 In the <b>Virtuoso.svc.cs</b> Data Service file created add the data source class name of <b>VirtuosoDemoEntities</b> (note this is the name set in step 12) as the <b>DataService</b> name and enable the access to the Data Service by adding the entry <b>config.SetEntitySetAccessRule("*", EntitySetRights.All);</b> in the <b>InitializeService</b> method. <verbatim> // C# using System; using System.Web; using System.Collections.Generic; using System.ServiceModel.Web; using System.Linq; using System.Data.Services; namespace SimpleDataService { public class Northwind : DataService<VirtuosoDemoEntities> { public static void InitializeService(IDataServiceConfiguration config) { config.SetEntitySetAccessRule("*", EntitySetRights.All); } } } </verbatim> %BR%%BR%<img src="%ATTACHURLPATH%/VirtAdoNetDataServices_16.png" style="wikiautogen"/>%BR%%BR% 1 To test the Data Service, simply hit <b>Ctrl+F5</b> within Visual Studio, which will start the development web server, run the Data Services server inside and load a Web browser page displaying the list of available tables/entities of the Demo database. %BR%%BR%<img src="%ATTACHURLPATH%/VirtAdoNetDataServices_17.png" style="wikiautogen"/>%BR%%BR% 1 To access a specific entity instance like the <b>Customers</b> table <b>ALFKI</b> record, this would be specified as <b><code><nowiki>http://host/vdir/Virtuoso.svc/Customers('ALFKI')</nowiki></code></b>. %BR%%BR%<img src="%ATTACHURLPATH%/VirtAdoNetDataServices_18.png" style="wikiautogen"/>%BR%%BR% ---++ NOTES 1 <b>Important</b> - To view <b>Atom</b> (the default format returned by an ADO.NET Data Service) in Internet Explorer, you must first ensure that <b>Feed Reading View</b> is turned <b>off</b> . This can be done on the <b>Content tab</b> of <b>Tools<b> in <b>Internet Options</b>.%BR%%BR% 1 If a Data Services entity instance URI page fails to load you can turn <b>Verbose</b> errors on by adding <b>config.UseVerboseErrors = true;</b> in the <b><code><nowiki>virtuoso.svc.cs InitializeService</nowiki></code></b> method to obtain more detailed information from the server as to why the page failed to load: <verbatim> public static void InitializeService(IDataServiceConfiguration config) { config.UseVerboseErrors = true; config.SetEntitySetAccessRule("*", EntitySetRights.All); } </verbatim>
sioc:id
184bac3b1ff13318aea6f30aee505a5e
sioc:link
n2:VirtUsingMsAdoNetDataServicesWithVirtuoso
sioc:has_container
n22:VOS
n27:has_services
n26:item
atom:title
VirtUsingMsAdoNetDataServicesWithVirtuoso
sioc:links_to
n7:VirtuosoDemoModel n7:DataService n7:VirtuosoDemoEntities n7:InitializeService n2:OpenLink
atom:source
n22:VOS
atom:author
n5:this
atom:published
2017-06-13T05:38:43Z
atom:updated
2017-06-29T07:41:48Z
sioc:topic
n22:VOS