From: Dick C. <di...@me...> - 2003-03-01 02:24:42
|
I don't really do VB, but I believe the import statement below is analogous to C#'s "using FirebirdSql.Data.Firebird". That being the case, the answer to your question is 'no'. Including the namespace does not link the DLL. All it accomplishes is allow you to type classes/members/methods in a shorter form without having to fully qualify them all the time. I think the closest analogy with VB is the "WITH" statement. For example, instead of writing: FirebirdSql.Data.Firebird.FbConnection myConnection = new FirebirdSql.Data.Firebird.FbConnection(connectionString); you can do: using FirebirdSql.Data.Firebird; FbConnection myConnection = new FbConnection(connectionString); Notice that I did not have to fully qualify FbConnection to its formal namespace because I included it in the 'using' statement. But that's all it does -- save you typing. It is not a mechanism to actually establish an association in your Assembly file. To do that, you need to setup a reference under the Solutions Explorer. Dick Andrew Goodall wrote: > Isn't that what the import namespace statement does ? > I have that included but it still cannot find the classes, such as > Fbconnection. > > <%@ import Namespace="FirebirdSql.Data.Firebird" %> > > -------------------------------------------------- > > > In Visual Studio, you would normally include the > FirbirdSql.Data.Firebird in the Solutions Explorer's References. This > sorts of binds your application to the DLL. Maybe you need to do > something similar with webmatrix. > > Dick > > > > Andrew Goodall wrote: > >> >>I'm using webmatrix free dev-app to do my developing, with VB on the >>codebehind. >> >>The error I receive on loading the webpage .aspx is: Type >>'FbConnection' is not defined >> >>which tells me its not finding the FirebirdSql.Data.Firebird class. > |