Dec 162004
 

With 10g Release 2 supporting .NET CLR from within the database, Oracle tries to take a piece of the .NET pie. With their announcement to release a Visual Studio .NET plugin, they show they’re eager to get that piece of the pie!

Oracle Developer Tools will be an add-in for Visual Studio .NET. It consists of an explorer to browse Oracle-schema’s, designers and wizards to create/alter schema’s, a PL/SQL editor, and the ability to drag-n-drop schema-objects onto your form and the code is automagically generated.

A beta version of the Developer Tools will be released at the end of this month. Watch this space.

 Posted by at 15:16
Dec 162004
 

If your company is a one-man-band, like mine, you’ll like this story: Finding a Product Idea for Your Micro-ISV.

 Posted by at 12:09
Dec 162004
 

In a follow-up to Perry’s post (again) I wonder: why should one buy Delphi 2005 instead of Visual Studio for .NET? A manager sees:

Delphi 2005 Architect edition: $3000 (new user). Support is an optional product. Cheapest level includes only 3 incidents for 12 months (whatever comes first).

MSDN Universal: $2800 (new user) and that gives the user VS.NET Enterprise Architect, ALL Office applications (including previous versions for testing), LTU (albeit for development only) for all Windows OS-es, including pre-releases only available to subscribers, online support with a garantueed response of 2 days, 4 phone incidents)

If you or your company has a history with Delphi and you want to keep your existing codebase, I can see why Delphi 2005 is a logical step. If you’re choosing tools for a new project, I cannot see why one would not choose MSDN Universal.

 Posted by at 10:51
Dec 162004
 

Yesterday I fooled around with the ODP.NET drivers from Oracle. Just to create a simple thing to proof the drivers worked, I dropped a OracleConnection and two buttons on a form, named one Connect and the other (guess what) Disconnect. I double-clicked on the Connect button, added a try-open-except-errormessage. At that time I didn’t notice the red underlining the .close statement had. I double-clicked on the Disconnect button and added a try-close-except-errormessage. F9. Delphi gave me an error on the open-property (duh, it’s not a property, it’s a procedure) of the Oracle-connection. I placed the cursor on the dot, removed the word “open” and the semicolon, and pressed Ctrl-Space. Hey, I thought, let Delphi do the work. I choose “procedure Close”, and pressed enter. Again, red underlining and still compiling did not work. WTF!?

Close all, save? No!

New C# project. Add Oracle-connection, and two buttons. No rename, just double-click. F*CK! (Excuse my French) C# needs () after a procedure with no arguments. F9. It works. I can connect and disconnect to my Oracle database.

WTF!?!?!?! Is Borland pushing us to use its C# to outphase Delphi???? 🙁

 Posted by at 08:42