Re: API or standard DLL?
- From: "Mr. Arnold" <MR. Arnold@xxxxxxxxxx>
- Date: Tue, 24 Jul 2007 21:25:59 GMT
<louw.elbie@xxxxxxxxx> wrote in message news:1185258062.689196.225340@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi there
I got a project where a client wants a API written to access external
product provider databases and return results as a recordset.
What is the difference between an API and standard DLL? As I
understand, API doesn't rely on any other
software than e.g. Windows APIs to perform a task?
Should one write the API in C++ or will VB.NET or C# work? If so,
will the API will depend on the dotNet framework to be loaded?
It doesn't matter what language use in writing code to return an ADO.Net recordset, which will be done by code you develop in a DLL that will do that for you. An API is another thing altogether.
A program written to interface with a database solution and a program written to use API(s) are two different things.
You would use ADO.NET which has many types of 3rd party database vendors or providers, like MS SQL Server, Oracle, Btrieve, Sybase, MySQL and many other providers, to provide solutions in ADO.NET to access their database.
.
- References:
- API or standard DLL?
- From: louw . elbie
- API or standard DLL?
- Prev by Date: Re: How important is software maintenance?
- Next by Date: Re: Help with Doxygen and C structs
- Previous by thread: Re: API or standard DLL?
- Next by thread: Re: API or standard DLL?
- Index(es):
Relevant Pages
|