Page 1 of 1

Problem installing, registering components for BDS 2006

Posted: Wed 20 Sep 2006 12:55
by labate
Hi,

I'm installing CoreLab OraDirect .NET for .NET v1.1 on a machine with Borland Developer Studio (BDS) 2006.

The CoreLab components are not present in the Installed .NET components list and there is no toolbox palette.

If I open a command window and type "gacutil /l", I can see the line :
CoreLab.Oracle, Version=3.50.12.0, Culture=neutral, PublicKeyToken=09af7300eec23701, Custom=null
I suppose the components are in the GAC, so what's wrong with the install?

I choose the option Custom, and selected all except the last one "Enterprise Library".

Thanks.
Adriano

Posted: Wed 20 Sep 2006 13:49
by Alexey
Did you try to browse our assembly manually?

Posted: Wed 20 Sep 2006 14:01
by labate
What do you mean by browsing the assembly?

What I've done is to copy "C:\Program Files\CoreLab\OraDirect.NET\CoreLab.Oracle.dll" to the "bin" directory of my Delphi project.

Then in BDS2006, I went on my project, "Add a reference...".
The "Add a reference" dialog opens and in the "Project references" tab, I did a "Browse..." to point on the "bin\CoreLab.Oracle.dll".

Maybe it is what you meant by "browse"...

It works, but what I expected is that the component installation places the component in the installed .net components and in the toolbox as said in the documentation.

Maybe that's an installation problem of the setup application. Not critical.

Best regards,
Adriano

Posted: Wed 20 Sep 2006 15:15
by Alexey
As described in our documentation, to register OraDirect .NET components in Delphi Tool Palette follow these steps:
1. Open Delphi IDE and go to "Tool Palette" window;
2. Add "OraDirect" category using popup menu;
3. Select "Installed .NET Components..." from popup menu;
4. Go to "Installed .NET Components" tab within opened dialog;
5. Check OracleConnection, OracleCommand, OracleDataAdapter, etc.;
6. Press OK button.
Since now OraDirect .NET components are available from Tool Palette.

By "browsing" i meant that if you cannot find said components in the appeared window you can browse to our assembly manually.

Posted: Wed 20 Sep 2006 15:19
by labate
Yes, that's the case.
The components did not appear in the installed .NET components window, so I had to browse the assembly to add a reference to my project.

Thank you.

Posted: Wed 20 Sep 2006 15:22
by Alexey
Well done.