🚀 go-pugleaf

Nexus Database Systems is pleased to announce our latest offering for .NET
development; a fully managed provider to be able to access data from a
NexusDB database server using ADO.NET. The provider does not rely on any
win32 dlls to function, which means that it will be able to be used with any
.NET environment:

- .NET hosted on windows
- Compact Framework (PocketPCs, SmartPhones etc)
- Mono
- etc...

The current beta contains:
---------------------
* a provider compiled for the normal .NET Framwork
* a provider compiled for the Compact Framework
* a demo for each of these
* a nxserver.exe that incorporates the needed Direct TCP protocol.

How does it work
----------------
The new provider has a ConnectionType property which decides if the
connection will be via a proxy DLL or using the new direct TCP mode. Direct
TCP needs a new "Transport" on the server side, which will be available in
full source to all our customers and compiled into the binaries available
from our webside (once the new version goes retail). The default port for
this TCP transport is
16080, but can be changed in the according settings on the NexusDB server
and via the ConnectionString property on the client. The two important
settings for the connectionString are
"Server=IpAddressOrName" and "Port=PortNumber".

Current Limitations
-------------------
* the provider communicates unencrypted with the server
* there's no user log-on challenged.
* Data sent from the client is in this version unpacked (data sent from the
server is packed with the zlib library though)
* the wizards are not updated to allow for the new TCP mode yet
* the CF provider currently seems quite slow (see below)
* the Direct TCP Protocol in the nxServer.exe will stop working after
October
15th.
* no DLL proxy delivered thus DLLProxy mode not possible except for current
owners of the ADO Provider.

Notes about the CF version
--------------------------
The compact framework has some severa limitations especially in reagards of
design time support and performance. Thus the CF provider was stripped from
all design time code and it is ver unlikely that it will have support for
wizards/ide designers (actually we don't think it is even possible).
In tests we realized that the CF provider is quite slow in converting the
data from the binary transmitted format to the correct .NET types. We are
not sure if this is due to the overall low speed on the devices/emulators
but we will take a closer look later in this beta phase. We haven't looked
at any other providers and their speed, so we're not sure yet, if this
should be of any
concern or we just have to accept it.


How to report problems/suggestions?
-----------------------------------
Please use the news://news.nexusdb.com/nexusdb.beta.dotNetProvider newsgroup
for
any reports or suggestions.

How to get it
-------------
Download it from here:
http://www.nexusdb.com/downloads/beta/nxADODirectBeta1.ZIP


Happy .NET'ing!


--

Eivind Bakkestuen
Nexus Database Systems
http://www.nexusdb.com