Print Page | Close Window

Design-time and runtime providers

Printed From: IdeaBlade
Category: DevForce
Forum Name: DevForce Classic
Forum Discription: For .NET 2.0
URL: http://www.ideablade.com/forum/forum_posts.asp?TID=143
Printed Date: 07-Apr-2025 at 1:22pm


Topic: Design-time and runtime providers
Posted By: Customer
Subject: Design-time and runtime providers
Date Posted: 12-Jul-2007 at 11:12am
I am preparing a presentation on DevForce for a group of Informix users. I know that the OleDb driver is required for the ORM tool. However, in a production environment, are customers switching to an ADO.Net provider for data access? Are there benefits to that approach? Problems? I think I remember from class that you *could* switch to an ADO.Net provider. I just don't remember if there are any good reasons to do so.

I ask partly for my presentation and partly because the ADO.Net 2.0 driver for Informix is now in beta. I know Microsoft's ADO.Net 2.0 has some significant performance benefits. I am wondering if these might help DevForce, too.


Replies:
Posted By: IdeaBlade
Date Posted: 12-Jul-2007 at 11:14am

To answer your question � yes, people do often switch to another provider at runtime.  At design-time we need an OLE-DB compliant provider to ensure that the scheme can be read successfully, but at run time most people are concerned with performance so if there�s a faster driver that works they will use it instead.  DevForce currently supports the SQL Server and Oracle .NET providers, and might need a little tweaking to recognize a new .NET provider, so I can�t promise that the Informix driver would work out of the box. Inverting your question, the reason people might stick with the OLE-DB provider at runtime is that it supports a broader array of databases.


Print Page | Close Window