[Firebird-net-provider] VS Studio Error Message (Assembly could not be loaded)

[Christopher W. <chr...@ad...>]

Hello,

The info below is based on my experience with VS.Net 2002, Firebird 1.5
RC1, Firebird Net-Provider RC3 and SibPro2 OLE DB provider.


> First: I've searched the mailing list, trying to
> figure out if Firebird will be showed in the Server
> Explorer in Visual Studio, but I couldn't find a
> reference to that. I still don't know. Wouldn't it be
> nice if this would be shown somewhere in the
> documentation?

I downloaded SIBProvider for the same reason and yes it does 
show up in the Server Explorer in Visual Studio;  However, if you try to
drag and drop a Firebird table from the server explorer on the Schema
design surface (if you try to create a typed dataset), the IDE displays
an error message The XML schema could not be interpreted from this
object :(  Microsoft's tools work best with their own db of course...

I have not had good luck using the designer with the Firebird
components;  I have found that it works better just writing the code. 
Another approach that has worked for me is to use MSDE tables with
schemas that are as close to Firebird as they can be to generate typed
datasets and then simply modify the code to work with Firebird.  Kind of
a pain, but it works.


> Second: I've just reinstalled my computer from
> scratch. Windows 2000 Professional SP3, Firebird 1.02
> Client, Visual Studio.NET 2002,
> FirebirdNetProvider-1.0-RC3. When I'm trying to
> reference the provider (Right-click on the Data Tab ->
> Customize Toolbox... -> .NET Framwork Components Tab
> -> Browse to FirebirdSql.Data.Firebird.dll) I got an
> error message saying "The assembly 'C:\Program
> Files\FirebirdNetProvider\FirebirdSql.Data.Firebird.dll'
> could not be loaded. Check that any dependencies the
> file requires are installed." What is missing, what
> should I do? Or I am doing the wrong way

I had the same problem.  Recompiling the dll with nant solved the
problem.  If you have downloaded mono for windows, just make sure
the path to the nant binary is in your path before the mono bin path as
they include an old version of nant with mono.



Best regards,
Paul