I have no problems setting up a regular (Windows Forms or Console) project in C# to use Firebird's .NET data provider.
However, whenever I try to use the same provider in ASP.NET I do the following:
- Copy the DLL to the project to keep it under version control
- Add the reference to the project
- Create an entry in
<connectionStrings/>
tag for my connection. - Try to use the entry to connect to Firebird
Here is the entry example:
<connectionStrings>
<add
name="cstringdbname"
connectionString="User=SYSDBA;Password=MY_PASS;Database=/opt/interbase/data/mydbname;Server=MyHostName; Connection lifetime=15;Pooling=true"
providerName="Firebird"/>
</connectionStrings>
I tried with different stuff in providerName
attribute. Nothing seems to work.
My problem is in step #4. Whenever I try connecting to the Database with a SqlDataSource component, the connection attempts to use SQLServer data provider instead of Firebird's, and I get an error.
My question: is there anything else I need to do in order to make ASP.NET to load, use, acknwoledges the existance of my Firebird provider?