Re: Moving from Delphi to Visual Studio. Smart move??

In article <40b6e7b4$0$48959$e4fe514c_at_news.xs4all.nl>, "Gijsie" <gijs.de.wolff_at_beheervisie_.nl> wrote:
>Does Visual Studio always asume you are working with MSSQL.

No. There are classes/objects for making connections to oracle.

>Will we have to use ODBC.

No. the "Data Provider for Oracle" objects (see above) use the Oracle client software. You can also make connections via ODBC and OLE DB, but I prefer the native connection.

>Can you keep deploying simple. (I want to have one exe that can run from a
>CD)

Providing the client already has the correct version of .NET framework installed (comes via microsoft update), deployment can be as simple as one exe... depends on how you develop the application. You can also generate installation packages (msi) for deployment.

>Can anyone please share their experience with developing in Visual Studio
>towards Oracle databases. And what version (Professional, Enterprise or
>Architect) do you recommend. And should I worry about totally different
>things?

So far for us, it's been fairly easy to do very complex "Windows" things... I cannot compare it to Delphi, as I've no experience with it, tho I've always heard good things. VS provides a common base of classes and objects, but you can write apps in VB, C#, C++, Visual FoxPro and/or J#. For VB writers especially (but not solely), the IDE is very programmer-friendly... It'll really spoil you. As far as Oracle goes, I doubt .NET's much different from Delphi, Powerbuilder, etc. in the way it works.

Worries? A few bugs to work around, but no show-stoppers so far.

Smart move?? As I've not used Delphi, I cannot say. Visual Studio, however, is a robust development environment for Windows programming... and quite capable with Oracle. I've experience with Oracle's Forms 6i and Powerbuilder 6 and I'd have absolutely no problems recommending a move to Visual Studio 2003 from there. Received on Fri May 28 2004 - 16:48:46 CEST