Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 7 of 7 total
Thread DBISAM ADO.Net Data Provider - VWD Express
Thu, Feb 2 2006 4:14 AMPermanent Link

"TorB."
Hi!
Anybody who have tried to use this tool in Visual Web Developer 2005 Express
Edition?
I have it installed normally in a way, but I am not capable of putting the
tools into the toolbox.
The discription on the producer's web site does not work by me.
Any help somewhere?
Kind regards
TorB.

Thu, Feb 2 2006 6:57 AMPermanent Link

Michael Baytalsky
Hi TorB,

I'm assuming you're using v.2.0.0 for ADO/.Net 2?
Were you able to add it to VS C# Express?
As readme.txt suggests, you need to create a group
in toolbox and add item (which you select from
list of installed assemblies). Make sure you have
2.0.0 installed into assembly cache.

Regards,
Michael

TorB. wrote:
> Hi!
> Anybody who have tried to use this tool in Visual Web Developer 2005 Express
> Edition?
> I have it installed normally in a way, but I am not capable of putting the
> tools into the toolbox.
> The discription on the producer's web site does not work by me.
> Any help somewhere?
> Kind regards
> TorB.
>
>
Thu, Feb 2 2006 9:38 AMPermanent Link

"TorB."
Hi Michael!
Thank you for a quick reply.
Yes I am using ver. 2.
No, I have the same problem in VS C# Express too.
Your install manual on your web site states this:
"
Microsoft Visual Studio.Net
1. Click on ToolBox/AddTab and specify a name for the new Tab "Dbisam.Net"
2. Select the new tab and click pop-up menu item Add/Remove Components...
3. Select DbisamClient.dll from .Net FrameWork Components List
"
Making a new tab. is OK, but I can not find the pop-up menu item "Add/Remove
components..."
The only relevant item is "Choose items..."
As far as I know this is only to move items which are already in the
toolbox.

Is it not possible to install this in the Express versions, maybe?

Kind regards
TorB.
**************


> I'm assuming you're using v.2.0.0 for ADO/.Net 2?
> Were you able to add it to VS C# Express?
> As readme.txt suggests, you need to create a group
> in toolbox and add item (which you select from
> list of installed assemblies). Make sure you have
> 2.0.0 installed into assembly cache.

Thu, Feb 2 2006 10:40 AMPermanent Link

Michael Baytalsky
Hi TorB,

> Making a new tab. is OK, but I can not find the pop-up menu item "Add/Remove
> components..."
> The only relevant item is "Choose items..."
> As far as I know this is only to move items which are already in the
> toolbox.
No, you're wrong. All the demos were developed using exactly Express
edition of C# and I was easily able to install the components into my
Express edition. You're correct about "Choose items..." though - I
used old readme and forgot to change the name from Add/Remove.
Other then that, readme is correct. Once you create a group and click
on choose, you will get a long list of components. Scroll down to
locate 4 dbisam related components (DbisamCommand, DbisamCommandBuilder,
DbisamConnection, DbisamDataAdapter). Check mark them and press okey.
The components will be added to newly created group in the toolbox.
If you don't have those components listed, then DbisamClient assembly is
not installed correctly into assembly cache. See bat files provided
to install the assembly manually.

Sincerely,
Michael
Thu, Feb 2 2006 12:22 PMPermanent Link

"TorB."
Hi again Michael!
I am very sorry to bother you this much, but I have done everything that you
are suggesting.
I finally managed to get the toolkit installed into C# Express by first
resetting the toolbox to it's default state. It is now working fine here, as
far as I can see Win.Net applications.
In VWD Express however I still have no success with web app. for ASP.Net. If
I select the "Show all" option in the toolbox  I can see the DBISAM ADO.Net
tools, but they are all greyed out and not accessable.
The version 1.6 is working fine in Delphi8 though Smile
Kind regards
TorB.

****

"Michael Baytalsky" <mike@contextsoft.com> skrev i melding
news:26699CD2-917A-47B8-85E7-C47B2ED8AF7B@news.elevatesoft.com...
> Hi TorB,
>
>> Making a new tab. is OK, but I can not find the pop-up menu item
>> "Add/Remove components..."
>> The only relevant item is "Choose items..."
>> As far as I know this is only to move items which are already in the
>> toolbox.
> No, you're wrong. All the demos were developed using exactly Express
> edition of C# and I was easily able to install the components into my
> Express edition. You're correct about "Choose items..." though - I
> used old readme and forgot to change the name from Add/Remove.
> Other then that, readme is correct. Once you create a group and click
> on choose, you will get a long list of components. Scroll down to
> locate 4 dbisam related components (DbisamCommand, DbisamCommandBuilder,
> DbisamConnection, DbisamDataAdapter). Check mark them and press okey.
> The components will be added to newly created group in the toolbox.
> If you don't have those components listed, then DbisamClient assembly is
> not installed correctly into assembly cache. See bat files provided
> to install the assembly manually.
>
> Sincerely,
> Michael

Sat, Feb 4 2006 1:51 PMPermanent Link

Michael Baytalsky
Hi TorB,

Sorry for delayed answer - I had to install and try VWD to understand
the problem. Before we begin, please, refer to readme file regarding
registering DbisamClient in machine.config file.

Now, the problem was: you cannot use DbisamDataAdaper as
a component to simply drop it onto aspx page. This is not supported
feature in Express edition, I guess (it doesn't support design-time things).
What you need to do is use SqlDataSource component (drop it onto aspx form)
and configure it manually (via object inspector) to access DbisamClient
provider. (Do not use standard configuration dialog, it won't work, because
MS never makes it easy for 3rd party and I'm yet to find any public
docs on how this should be registered).

If DbisamClient is registered in machine.config file correctly,
you will be able to select its name in DataProvider property of
SqlDataSource component and specify ConnectionString and
SelectCommand (and other commands if necessary). Then connect your
GridView to SqlDataSource and... hold on, not just yet Wink.
Open your Web.Config file for the project and add there (under
<configuration> section)
    <system.data>
        <DbProviderFactories>
           <add name="DBISAM Data Provider" invariant="DbisamClient"
description="DBISAM .Net Data Provider"
type="DbisamClient.DbisamClientFactory, DbisamClient, Version=2.0.0.0,
Culture=neutral, PublicKeyToken=f06b6d18bf0b8db8"/>
        </DbProviderFactories>
    </system.data>

Now you can run your web site and it should work.
Another method, used in out Demos (Asp.Net) is to create adapter manually
and assign DataSource property of your GridView manually also.

I will give this more research and probably post another demo regarding
VWD. I'm actually planning to use it in my next web project, so I'll
have to learn this thing...

Regards,
Michael

TorB. wrote:
> Hi again Michael!
> I am very sorry to bother you this much, but I have done everything that you
> are suggesting.
> I finally managed to get the toolkit installed into C# Express by first
> resetting the toolbox to it's default state. It is now working fine here, as
> far as I can see Win.Net applications.
> In VWD Express however I still have no success with web app. for ASP.Net. If
> I select the "Show all" option in the toolbox  I can see the DBISAM ADO.Net
> tools, but they are all greyed out and not accessable.
> The version 1.6 is working fine in Delphi8 though Smile
> Kind regards
> TorB.
>
> ****
>
> "Michael Baytalsky" <mike@contextsoft.com> skrev i melding
> news:26699CD2-917A-47B8-85E7-C47B2ED8AF7B@news.elevatesoft.com...
>> Hi TorB,
>>
>>> Making a new tab. is OK, but I can not find the pop-up menu item
>>> "Add/Remove components..."
>>> The only relevant item is "Choose items..."
>>> As far as I know this is only to move items which are already in the
>>> toolbox.
>> No, you're wrong. All the demos were developed using exactly Express
>> edition of C# and I was easily able to install the components into my
>> Express edition. You're correct about "Choose items..." though - I
>> used old readme and forgot to change the name from Add/Remove.
>> Other then that, readme is correct. Once you create a group and click
>> on choose, you will get a long list of components. Scroll down to
>> locate 4 dbisam related components (DbisamCommand, DbisamCommandBuilder,
>> DbisamConnection, DbisamDataAdapter). Check mark them and press okey.
>> The components will be added to newly created group in the toolbox.
>> If you don't have those components listed, then DbisamClient assembly is
>> not installed correctly into assembly cache. See bat files provided
>> to install the assembly manually.
>>
>> Sincerely,
>> Michael
>
>
Sun, Feb 5 2006 12:35 PMPermanent Link

"TorB."
Hi Michael!
Thank you very much for a very good explanation. I will make a hard copy of
this for future references.
You know, my main tool is Delphi, but I am also looking into VWD to see  if
it is usable for me. It is very simple to use fi. MSSQL in this tool, but my
main goal is to stick to DBISAM for the time being.
Now I am only looking forward to the date when you release a version for
Delphi2006 Smile
Kind regards
TorB.

*****

"Michael Baytalsky" <mike@contextsoft.com> skrev i melding
news:73908744-F725-47A5-B6F2-11AA6690B5D0@news.elevatesoft.com...
> Hi TorB,
>
> Sorry for delayed answer - I had to install and try VWD to understand
> the problem. Before we begin, please, refer to readme file regarding
> registering DbisamClient in machine.config file.
>
> Now, the problem was: you cannot use DbisamDataAdaper as
> a component to simply drop it onto aspx page. This is not supported
> feature in Express edition, I guess (it doesn't support design-time
> things).
> What you need to do is use SqlDataSource component (drop it onto aspx
> form)
> and configure it manually (via object inspector) to access DbisamClient
> provider. (Do not use standard configuration dialog, it won't work,
> because
> MS never makes it easy for 3rd party and I'm yet to find any public
> docs on how this should be registered).
>
> If DbisamClient is registered in machine.config file correctly,
> you will be able to select its name in DataProvider property of
> SqlDataSource component and specify ConnectionString and
> SelectCommand (and other commands if necessary). Then connect your
> GridView to SqlDataSource and... hold on, not just yet Wink.
> Open your Web.Config file for the project and add there (under
> <configuration> section)
>     <system.data>
>         <DbProviderFactories>
>            <add name="DBISAM Data Provider" invariant="DbisamClient"
> description="DBISAM .Net Data Provider"
> type="DbisamClient.DbisamClientFactory, DbisamClient, Version=2.0.0.0,
> Culture=neutral, PublicKeyToken=f06b6d18bf0b8db8"/>
>         </DbProviderFactories>
>     </system.data>
>
> Now you can run your web site and it should work.
> Another method, used in out Demos (Asp.Net) is to create adapter manually
> and assign DataSource property of your GridView manually also.
>
> I will give this more research and probably post another demo regarding
> VWD. I'm actually planning to use it in my next web project, so I'll
> have to learn this thing...
>
> Regards,
> Michael
>
> TorB. wrote:
>> Hi again Michael!
>> I am very sorry to bother you this much, but I have done everything that
>> you are suggesting.
>> I finally managed to get the toolkit installed into C# Express by first
>> resetting the toolbox to it's default state. It is now working fine here,
>> as far as I can see Win.Net applications.
>> In VWD Express however I still have no success with web app. for ASP.Net.
>> If I select the "Show all" option in the toolbox  I can see the DBISAM
>> ADO.Net tools, but they are all greyed out and not accessable.
>> The version 1.6 is working fine in Delphi8 though Smile
>> Kind regards
>> TorB.
>>
>> ****
>>
>> "Michael Baytalsky" <mike@contextsoft.com> skrev i melding
>> news:26699CD2-917A-47B8-85E7-C47B2ED8AF7B@news.elevatesoft.com...
>>> Hi TorB,
>>>
>>>> Making a new tab. is OK, but I can not find the pop-up menu item
>>>> "Add/Remove components..."
>>>> The only relevant item is "Choose items..."
>>>> As far as I know this is only to move items which are already in the
>>>> toolbox.
>>> No, you're wrong. All the demos were developed using exactly Express
>>> edition of C# and I was easily able to install the components into my
>>> Express edition. You're correct about "Choose items..." though - I
>>> used old readme and forgot to change the name from Add/Remove.
>>> Other then that, readme is correct. Once you create a group and click
>>> on choose, you will get a long list of components. Scroll down to
>>> locate 4 dbisam related components (DbisamCommand, DbisamCommandBuilder,
>>> DbisamConnection, DbisamDataAdapter). Check mark them and press okey.
>>> The components will be added to newly created group in the toolbox.
>>> If you don't have those components listed, then DbisamClient assembly is
>>> not installed correctly into assembly cache. See bat files provided
>>> to install the assembly manually.
>>>
>>> Sincerely,
>>> Michael
>>
Image