DatabaseDependencies Constructors
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Overloads
| DatabaseDependencies(IQueryCompilationContextFactory) |
Creates the service dependencies parameter object for a Database. Do not call this constructor directly from either provider or application code as it may change as new dependencies are added. Instead, use this type in your constructor so that an instance will be created and injected automatically by the dependency injection container. To create an instance with some dependent services replaced, first resolve the object from the dependency injection container, then replace selected services using the 'With...' methods. Do not call the constructor at any point in this process. |
| DatabaseDependencies(IQueryCompilationContextFactory, IUpdateAdapterFactory) |
Creates the service dependencies parameter object for a Database. Do not call this constructor directly from either provider or application code as it may change as new dependencies are added. Instead, use this type in your constructor so that an instance will be created and injected automatically by the dependency injection container. To create an instance with some dependent services replaced, first resolve the object from the dependency injection container, then replace selected services using the 'With...' methods. Do not call the constructor at any point in this process. This is an internal API that supports the Entity Framework Core infrastructure and not subject to the same compatibility standards as public APIs. It may be changed or removed without notice in any release. You should only use it directly in your code with extreme caution and knowing that doing so can result in application failures when updating to a new Entity Framework Core release. |
| DatabaseDependencies(IQueryCompilationContextFactory, IUpdateAdapterFactory, IDiagnosticsLogger<DbLoggerCategory.Update>) |
This is an internal API that supports the Entity Framework Core infrastructure and not subject to the same compatibility standards as public APIs. It may be changed or removed without notice in any release. You should only use it directly in your code with extreme caution and knowing that doing so can result in application failures when updating to a new Entity Framework Core release. |
DatabaseDependencies(IQueryCompilationContextFactory)
- Source:
- DatabaseDependencies.cs
- Source:
- DatabaseDependencies.cs
Creates the service dependencies parameter object for a Database.
Do not call this constructor directly from either provider or application code as it may change as new dependencies are added. Instead, use this type in your constructor so that an instance will be created and injected automatically by the dependency injection container. To create an instance with some dependent services replaced, first resolve the object from the dependency injection container, then replace selected services using the 'With...' methods. Do not call the constructor at any point in this process.
public DatabaseDependencies (Microsoft.EntityFrameworkCore.Query.IQueryCompilationContextFactory queryCompilationContextFactory);new Microsoft.EntityFrameworkCore.Storage.DatabaseDependencies : Microsoft.EntityFrameworkCore.Query.IQueryCompilationContextFactory -> Microsoft.EntityFrameworkCore.Storage.DatabaseDependenciesPublic Sub New (queryCompilationContextFactory As IQueryCompilationContextFactory)Parameters
- queryCompilationContextFactory
- IQueryCompilationContextFactory
Factory for compilation contexts to process LINQ queries.
Applies to
DatabaseDependencies(IQueryCompilationContextFactory, IUpdateAdapterFactory)
- Source:
- DatabaseDependencies.cs
- Source:
- DatabaseDependencies.cs
- Source:
- DatabaseDependencies.cs
- Source:
- DatabaseDependencies.cs
Creates the service dependencies parameter object for a Database.
Do not call this constructor directly from either provider or application code as it may change as new dependencies are added. Instead, use this type in your constructor so that an instance will be created and injected automatically by the dependency injection container. To create an instance with some dependent services replaced, first resolve the object from the dependency injection container, then replace selected services using the 'With...' methods. Do not call the constructor at any point in this process.
This is an internal API that supports the Entity Framework Core infrastructure and not subject to the same compatibility standards as public APIs. It may be changed or removed without notice in any release. You should only use it directly in your code with extreme caution and knowing that doing so can result in application failures when updating to a new Entity Framework Core release.
[Microsoft.EntityFrameworkCore.Infrastructure.EntityFrameworkInternal]
public DatabaseDependencies (Microsoft.EntityFrameworkCore.Query.IQueryCompilationContextFactory queryCompilationContextFactory, Microsoft.EntityFrameworkCore.Update.IUpdateAdapterFactory updateAdapterFactory);[<Microsoft.EntityFrameworkCore.Infrastructure.EntityFrameworkInternal>]
new Microsoft.EntityFrameworkCore.Storage.DatabaseDependencies : Microsoft.EntityFrameworkCore.Query.IQueryCompilationContextFactory * Microsoft.EntityFrameworkCore.Update.IUpdateAdapterFactory -> Microsoft.EntityFrameworkCore.Storage.DatabaseDependenciesPublic Sub New (queryCompilationContextFactory As IQueryCompilationContextFactory, updateAdapterFactory As IUpdateAdapterFactory)Parameters
- queryCompilationContextFactory
- IQueryCompilationContextFactory
- updateAdapterFactory
- IUpdateAdapterFactory
- Attributes
Applies to
DatabaseDependencies(IQueryCompilationContextFactory, IUpdateAdapterFactory, IDiagnosticsLogger<DbLoggerCategory.Update>)
- Source:
- DatabaseDependencies.cs
- Source:
- DatabaseDependencies.cs
- Source:
- DatabaseDependencies.cs
This is an internal API that supports the Entity Framework Core infrastructure and not subject to the same compatibility standards as public APIs. It may be changed or removed without notice in any release. You should only use it directly in your code with extreme caution and knowing that doing so can result in application failures when updating to a new Entity Framework Core release.
[Microsoft.EntityFrameworkCore.Infrastructure.EntityFrameworkInternal]
public DatabaseDependencies (Microsoft.EntityFrameworkCore.Query.IQueryCompilationContextFactory queryCompilationContextFactory, Microsoft.EntityFrameworkCore.Update.IUpdateAdapterFactory updateAdapterFactory, Microsoft.EntityFrameworkCore.Diagnostics.IDiagnosticsLogger<Microsoft.EntityFrameworkCore.DbLoggerCategory.Update> logger);[<Microsoft.EntityFrameworkCore.Infrastructure.EntityFrameworkInternal>]
new Microsoft.EntityFrameworkCore.Storage.DatabaseDependencies : Microsoft.EntityFrameworkCore.Query.IQueryCompilationContextFactory * Microsoft.EntityFrameworkCore.Update.IUpdateAdapterFactory * Microsoft.EntityFrameworkCore.Diagnostics.IDiagnosticsLogger<Microsoft.EntityFrameworkCore.DbLoggerCategory.Update> -> Microsoft.EntityFrameworkCore.Storage.DatabaseDependenciesPublic Sub New (queryCompilationContextFactory As IQueryCompilationContextFactory, updateAdapterFactory As IUpdateAdapterFactory, logger As IDiagnosticsLogger(Of DbLoggerCategory.Update))Parameters
- queryCompilationContextFactory
- IQueryCompilationContextFactory
- updateAdapterFactory
- IUpdateAdapterFactory
- Attributes
Remarks
Do not call this constructor directly from either provider or application code as it may change as new dependencies are added. Instead, use this type in your constructor so that an instance will be created and injected automatically by the dependency injection container. To create an instance with some dependent services replaced, first resolve the object from the dependency injection container, then replace selected services using the C# 'with' operator. Do not call the constructor at any point in this process.
Applies to
Entity Framework