[ http://issues.apache.org/jira/browse/IBATISNET-47?page=all ]
Gilles Bayon closed IBATISNET-47:
---------------------------------
Resolution: Fixed
Fix Version: DataMapper 1.2
in SVN
> providers.config Assumes Types Are In The Same Assembly
> -------------------------------------------------------
>
> Key: IBATISNET-47
> URL: http://issues.apache.org/jira/browse/IBATISNET-47
> Project: iBatis for .NET
> Type: Bug
> Environment: SharpHSQL data provider, Win32, .NET v1.1
> Reporter: Rick
> Assignee: Gilles Bayon
> Priority: Minor
> Fix For: DataMapper 1.2
>
> In one's providers.config file, the 'assemblyName' attribute of the
> <provider/> element is used to name the assembly that iBatis.NET will look
> into to discover all of the rest of the types that describe that provider.
> The 'parameterDbTypeClass' for the SharpHSQL ADO.NET provider is the
> SqlDbType class from the System.Data namespace of the System.Data assembly.
> All of the rest of the SharpHSQL ADO.NET provider classes (such as it's
> IDbConnection, etc) are in the SharpHSQL assembly.
> Is there an easy way to say (in effect, 'whoah, look in the named assembly
> for all the other types, but look in the System.Data assembly for this
> class'? Perhaps if the value assigned to the 'assemblyName' attribute was a
> fully assembly qualified Type name the parser would look into the inline
> assembly instead of the top level one (set to by the value 'assemblyName'
> attribute').
> I'm using the latest SharpHSQL binaries and the 1.1.458.0 build of iBatis.NET
> (pretty old I know).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
