Example for AddLinqToDBContext<TContext, TContextImplementation>

[s-kotte]

I'm trying to use the AddLinqToDBContext<TContext, TContextImplementation> method in my ASP.NET Core application to resolve an interface instead of the concrete class in my controllers. I am getting the following error message:

Unable to resolve service for type 'LinqToDB.DataOptions`1[Identity.SetupConfiguration.DB.DbConnection]' while attempting to activate 'Identity.SetupConfiguration.DB.DbConnection'.

My DbConnection class:

public class DbConnection: DataConnection, IDbConnection
{
    public DbConnection(DataOptions<DbConnection> options) : base(options.Options)
    {
    }

    public ITable<UserDb> User => this.GetTable<UserDb>();
}

public interface IDbConnection: IDataContext
{
    public ITable<UserDb> User { get; }
}

I've also registered the DataConnection in Startup.cs like this:

builder.Services.AddLinqToDBContext<IDbConnection, DbConnection>((provider, options) => options
    .UsePostgreSQL(builder.Configuration.GetConnectionString("Default")!)
    .UseDefaultLogging(provider));

[MaceWindu]

Change public DbConnection(DataOptions<DbConnection> options) to public DbConnection(DataOptions<IDbConnection> options)

[s-kotte]

Thanks, do I need to wait until issue #4326 is fixed or am I still doing something wrong? I now get the error Missing constructor accepting 'DataOptions' on type DbConnection.

[MaceWindu]

Add second constructor for now:

public DbConnection(DataOptions<IDbConnection> options) : base(options.Options)
{
}
public DbConnection(DataOptions<DbConnection> options) : base(options.Options)
{
}

issue will be fixed in next release

[MaceWindu]

@linq2db, any idea why we use TContext instead of TContextImplementation ?

[MaceWindu]

That's actually bug... We pass TContextImplementation to HasTypedContextConstructor but use TContext for registration

[MaceWindu]

Filled issue #4326, should be an easy fix