VB.Net Access

[davidtriggs]

Any chance that the File Geodatabase API will be made availble to those of us with simple minds and can only code in VB.net?

Alternatively, can you use these DLL's to work in VB and are there any samples available? Preferably with pictures.

Thanks

David

[lshipman]

We plan to release a .Net wrapper for the API in the next few months.

[Hornbydd]

This is good news, I program only in VB so looking forward to using the new File GeoDatabase API through VB .Net.

Duncan

[davidtriggs]

Thanks Lance, thats is good news, is there a rough release date?

[lshipman]

We hope to have it out no later than the end of July.

[rfrank5356]

Hi Lance - Is there a description of the proposed functions? I have flight planning software that currently takes in a kml file and spits out a flight plan based upon track width, altitude and other factors. My customes would prefer to give me shape files . . . so - whats cookin?

[vangelo]

If you download the C++ API, the HTML documentation (in the 'doc' directory - surf to index.html)
will tell you the objects which are accessible; the .Net wrapper classes could be expected to align
with them (tables and rows, with a geodatabase parent container and a number of geometry
accessor classes).

The FileGDB API uses the shapefile spec to transfer individual geometries in binary form, but there
is no support for shapefile access (read or write).

If you google 'shapefile specification' you'll find a number of links to the specification itself (which
is included in the FGBDAPI docs), plus the Wikipedia site (which has links to open-source shapefile
access APIs).

- V

[lshipman]

The function list matches the C++ API. As Vince notes the API does not read or write shapefiles. You might want to look at http://arcscripts.esri.com/details.asp?dbid=17013 which provides a OCX and DLL for reading and writing shapefiles.

[davidtriggs]

Hi Guys,
I was wondering if there had been any development on the VB.Net version of the File Geodatabase API?

Thanks

David

[vangelo]

The 1.1 API was released in August. Lance's "sticky" post details the changes and other
posts detail issues that have been found with the .NET API.

- V