ADOProvider V2 w/VS2005 support
 

Hannes,

You posted the following in nexusdb.beta.dotNetProvider 2006-03-23:

<< A new build 19 for .NETV1 was sent to customers. A time restricted
version for all others interested in testing and a .NETV2 (incl VS2005
integration) will follow very soon. >>

Any news regarding the .NET V2 version with VS2005 integration ?

I'm posting here in hope to get an answer, since you don't seem to read the
beta.dotNetProvider group (:

Ole

Re: ADOProvider V2 w/VS2005 support
 

Ole Willy Tuv wrote:

> Hannes,
>
> You posted the following in nexusdb.beta.dotNetProvider 2006-03-23:
>
> << A new build 19 for .NETV1 was sent to customers. A time restricted
> version for all others interested in testing and a .NETV2 (incl VS2005
> integration) will follow very soon. >>
>
> Any news regarding the .NET V2 version with VS2005 integration ?

Unfortunately not much further than on the date of above posting :(

--

Hannes Danzl [NexusDB Developer]
Newsgroup archive at http://www.tamaracka.com/search.htm

Re: ADOProvider V2 w/VS2005 support
 

Hannes,

> Unfortunately not much further than on the date of above posting :(

Thought so (:

Well, I converted to SQL Server a long time ago. The reason should be pretty
obvious.

Ole

Re: ADOProvider V2 w/VS2005 support
 

It can go really fast in this world... For new projects, we decided to
move to VS 2005 instead of Delphi (mainly because they are way to slow
in adapting .NET 2.0), and because we can't wait any longer for a
finished NexusDB .Net product, SQLServer will be our choice too...

I'm not quite sure what happened @ Nexus, quality and speed of updates
changed a lot between 1.x and 2.x :-(


Ole Willy Tuv schreef:

> Hannes,
>
>
>> Unfortunately not much further than on the date of above posting :(
>
>
>
> Thought so (:
>
> Well, I converted to SQL Server a long time ago. The reason should be
pretty obvious.
>
> Ole
>
Ole Willy Tuv schreef:
> Hannes,
>
>
>>Unfortunately not much further than on the date of above posting :(
>
>
> Thought so (:
>
> Well, I converted to SQL Server a long time ago. The reason should be pretty
> obvious.
>
> Ole
>
>

Re: ADOProvider V2 w/VS2005 support
 

> Well, I converted to SQL Server a long time ago. The reason should be
> pretty obvious.

For the idly curious; what commercially available database-based programs
are you currently maintaining?

--

Eivind Bakkestuen
Nexus Database Systems

Re: ADOProvider V2 w/VS2005 support
 

"Eivind Bakkestuen [NDD]" <Ieivind.bakkestuenHATE@nexusdb.comSPAM> wrote in
message news:444c209a@wic040d....
>> Well, I converted to SQL Server a long time ago. The reason should be
>> pretty obvious.
>
> For the idly curious; what commercially available database-based programs
> are you currently maintaining?

What the heck do you mean ?

Are you implying that since I've converted from NexusDB to SQL Server, I'm
obviously working on "commercially available" software ?

I'm maintaining a couple of ADO/ODBC projects, but I'm mainly developing my
database applications in VS 2005. In my newer projects, I'm developing db
agnostic data access classes based on the Microsoft Data Access Application
Block and/or the new abstracted db classes in ADO.NET 2.

If you'd have a look in beta.dotNetProvider, you'll see that I've made a lot
of input to Hannes regarding bugs, flaws and shortcomings in the
ADOProvider. The reason I've switched to SQL Server is the slow development
and poor support of the drivers. I'm aware of other developers who have lost
their patience as well.

The current situation, 10 months after the v2 release, is:

- Unfinished ADO.NET provider
- Unfinished DBExpress driver
- Poor performing ODBC driver

I hope this explains why I've converted to SQL Server.

Ole

Re: ADOProvider V2 w/VS2005 support
 

> Are you implying that since I've converted from NexusDB to SQL
> Server, I'm obviously working on "commercially available" software ?

No, but you are stating publicly that our products are not working well
enough to use in your projects. I am not going to contest that, everybody's
product is different, but it believe its informative for everyone reading
this to know what type of products we are talking about (I don't currently
know, which is why I am asking). We have also had feedback from customers
who are confused that there are good reports one day, and the next its not
good enough for use.

> The current situation, 10 months after the v2 release, is:
> - Unfinished ADO.NET provider

The main thing missing is VS 2005 integration. I believe Hannes is close to
finishing that; the provider should be useable via code.

> - Unfinished DBExpress driver

There has been very little demand for this driver, which is why it has not
been finished.

> - Poor performing ODBC driver

It might not win every speed contest, but for general use, it should be
quite ok now.

--

Eivind Bakkestuen
Nexus Database Systems

Re: ADOProvider V2 w/VS2005 support
 

<< No, but you are stating publicly that our products are not working well
enough to use in your projects. >>

In that case, your question was pretty weird.

<< I am not going to contest that, everybody's product is different, but it
believe its informative for everyone reading this to know what type of
products we are talking about (I don't currently know, which is why I am
asking). >>

I've explained what kind of data access stuff I'm coding. I've never got it
fully working with the beta ADOProvider, and the ODBC driver still have
issues in ADO mode. In addition, the beta ADOProvider regularly expired
without an update being published for weeks.

If you don't understand why I and other developers coding ADO.NET database
applications eventually lost our patience, I'm afraid I can't help you.

<< We have also had feedback from customers who are confused that there are
good reports one day, and the next its not good enough for use. >>

You need to distinguish between the work/reports I'm doing on a voluntary
basis related to the SQL engine and the needs/requirements I have for my
personal projects.

Ole

Re: ADOProvider V2 w/VS2005 support
 

>> The current situation, 10 months after the v2 release, is:
>> - Unfinished ADO.NET provider
>
> The main thing missing is VS 2005 integration. I believe Hannes is close to
> finishing that; the provider should be useable via code.

We have a project to start with VS 2005.

We won't do that without VS2005 integration.


>> - Unfinished DBExpress driver
>
> There has been very little demand for this driver, which is why it has not
> been finished.

Is there little demand, because the driver is not available?

>> - Poor performing ODBC driver
>
> It might not win every speed contest, but for general use, it should be
> quite ok now.

It's slow compared to another database i use, really slow.

Hannes is working on this issue and i am looking forward
to the improvements.


Thomas

Re: ADOProvider V2 w/VS2005 support
 

Eivind Bakkestuen [NDD] schreef:
> The main thing missing is VS 2005 integration. I believe Hannes is close to
> finishing that; the provider should be useable via code.

Sorry Eivind, but the main problem is that the provider expires all the
time without an update being available. Actually, I have no idea WHY
there's an expiration... If I remember correctly, my company payed for
the .NET provider in june last year, but today we can't ship a product
that is using it.

We will still using NexusDB for the Delphi Win32 applications that are
still being maintained in the company, but for new stuff, we can't
afford to wait any longer...