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

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

PrefixNamespace IRI
dctermshttp://purl.org/dc/terms/
atomhttp://atomowl.org/ontologies/atomrdf#
foafhttp://xmlns.com/foaf/0.1/
n12http://vos.openlinksw.com/dataspace/owiki/wiki/VOS/VirtProgressEntityFrameworkUsage/sioc.
n9http://vos.openlinksw.com/dataspace/services/wiki/
oplhttp://www.openlinksw.com/schema/attribution#
n2http://vos.openlinksw.com/dataspace/owiki/wiki/VOS/
dchttp://purl.org/dc/elements/1.1/
n10http://vos.openlinksw.com/dataspace/dav#
rdfshttp://www.w3.org/2000/01/rdf-schema#
n8http://rdfs.org/sioc/services#
siocthttp://rdfs.org/sioc/types#
n7http://vos.openlinksw.com/dataspace/person/dav#
n15http://vos.openlinksw.com/dataspace/owiki/wiki/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n6http://vos.openlinksw.com/dataspace/owiki#
xsdhhttp://www.w3.org/2001/XMLSchema#
n17http://vos.openlinksw.com/dataspace/person/owiki#
siochttp://rdfs.org/sioc/ns#
n18http://wikis.openlinksw.com/dataspace/owiki/wiki/UdaWikiWeb/
Subject Item
n7:this
foaf:made
n2:VirtProgressEntityFrameworkUsage
Subject Item
n10:this
sioc:creator_of
n2:VirtProgressEntityFrameworkUsage
Subject Item
n9:item
n8:services_of
n2:VirtProgressEntityFrameworkUsage
Subject Item
n6:this
sioc:creator_of
n2:VirtProgressEntityFrameworkUsage
Subject Item
n15:VOS
sioc:container_of
n2:VirtProgressEntityFrameworkUsage
atom:entry
n2:VirtProgressEntityFrameworkUsage
atom:contains
n2:VirtProgressEntityFrameworkUsage
Subject Item
n2:VirtProgressEntityFrameworkUsage
rdf:type
atom:Entry sioct:Comment
dcterms:created
2017-06-13T05:42:59.447614
dcterms:modified
2017-06-29T07:39:36.146434
rdfs:label
VirtProgressEntityFrameworkUsage
foaf:maker
n17:this n7:this
dc:title
VirtProgressEntityFrameworkUsage
opl:isDescribedUsing
n12:rdf
sioc:has_creator
n10:this n6:this
sioc:content
%VOSWARNING% %META:TOPICPARENT{name="VirtAdoNet35Provider"}% ---+ Using Microsoft Entity Frameworks to Access Progress Schema Objects with Virtuoso This document details the steps required to provide Microsoft Entity Framework access to Progress Schema Objects using the <nop>OpenLink Virtuoso Universal Server. This is achieved by Linking the required Progress Schema objects into Virtuoso using its built-in Virtual Database engine and then using the Virtuoso ADO.Net Entity Framework provider to query the remote Progress Schema objects linked into the Virtuoso Server. %TOC% ---++ Prerequisites The following must be in place to complete this exercise. 1 <b>Microsoft Visual Studio 2008 SP1 (or later)</b>%BR% Microsoft Visual Studio 2008 Service Pack 1 (or later) is required, as previous versions do not include the necessary Entity Framework support.%BR%%BR% 1 <b>Virtuoso ADO.NET Entity Framework Provider, v5.10 or later</b>%BR% The ADO.NET Entity Framework Provider must be installed on the Visual Studio development and deployment host(s). Version 5.10.x or later is required, as previous versions do not include the necessary Entity Frameworks support.%BR%%BR% 1 <b>Virtuoso Universal Server, v5.10 or later</b>%BR% Virtuoso Universal Server Release 5.10 or later is required, as previous versions do not include the necessary Entity Frameworks support. This may be on any host which is TCP/IP accessible from the Visual Studio development and deployment host(s).%BR%%BR% 1 <b>ODBC Driver for Progress</b>%BR% The Virtuoso Server uses an ODBC Driver for Progress to link in the Progress Schema Objects. The <b><nop>OpenLink Single-Tier ODBC Driver for Progress (SQL-92)</b> will be used in this document, and a functional ODBC Data Source Name (DSN) of "<b><code>prs101c</code></b>" will be assumed to exist on the machine hosting the Virtuoso Server. Any ODBC compliant driver for Progress should work.%BR%%BR% 1 <b>Progress DBMS</b>%BR% An Progress DBMS hosting the required Schema Objects needs to be available. This may be on any host which is TCP/IP accessible from the Virtuoso Server host. In this document, the Progress <nop>OpenEdge 10 <b>isports</b> database will be used to demonstrate the process.%BR%%BR% ---++ Tasks 1 <b>Ensure Progress Primary Keys (PKs) are not nullable</b>%BR% The Visual Studio 2008 Entity Data Model (EDM) requires that all primary keys are *NOT* Nullable, and will fail to generate an EDM if any are. Therefore, ensure any applicable primary keys are defined as not nullable in the Progress database schema before attempting to generate an EDM. In the case of the Progress isports database, several primary keys (PKs) *are* nullable. This issue is best addressed in the database schema, by [[VirtProgressPKNull][redefining those nullable PKs]] to be non-nullable (or *Mandatory*, in the terms Progress uses).%BR%%BR% 1 <b>[[http://wikis.openlinksw.com/dataspace/owiki/wiki/UdaWikiWeb/InstallConfigODBC][Install and configure the <nop>OpenLink ODBC Driver for Progress (SQL-92)]]</b>%BR%%BR% 1 <b>[[VirtADOClientServInstall][Install and configure <nop>OpenLink Virtuoso Universal Server]]</b>%BR%%BR% 1 <b>[[VirtProgressLinkingObjects][Link Progress tables and other schema objects into OpenLink Virtuoso]]</b>%BR%%BR% 1 <b>[[VirtProgressEDM][Create a Visual Studio-hosted Entity Data Model (EDM)]]</b>%BR%%BR%If entity-linking associations (i.e., Foreign Keys) are not automatically created (as they are not here with Progress), the [[VirtProgressAssociations][associations must be created manually]].%BR%%BR% 1 <b>[[VirtEntityFrameworkProgressDatService][Use the EDM to create an Entity Frameworks-based ADO.NET Data Service]]</b>%BR%%BR% 1 <b>[[VirtProgressVisualStudioDataGridFormsApp][Use the EDM to create an Entity Frameworks-based Windows DataGrid Form Application]]</b>%BR% CategoryDocumentation CategoryVirtuoso CategoryEntityFrameworks CategoryDotNET CategoryProgress
sioc:id
a4e1108afe574eac0d59e4e6490d067a
sioc:link
n2:VirtProgressEntityFrameworkUsage
sioc:has_container
n15:VOS
n8:has_services
n9:item
atom:title
VirtProgressEntityFrameworkUsage
sioc:links_to
n2:CategoryDocumentation n2:CategoryDotNET n2:VirtProgressLinkingObjects n2:CategoryProgress n2:CategoryVirtuoso n2:VirtADOClientServInstall n2:VirtEntityFrameworkProgressDatService n2:VirtProgressAssociations n2:VirtProgressPKNull n18:InstallConfigODBC n2:CategoryEntityFrameworks n2:VirtProgressEDM
atom:source
n15:VOS
atom:author
n7:this
atom:published
2017-06-13T05:42:59Z
atom:updated
2017-06-29T07:39:36Z
sioc:topic
n15:VOS