Global Data Management Forum

 View Only
Expand all | Collapse all

dotnet 7 / ef core 7 ?

  • 1.  dotnet 7 / ef core 7 ?

    Posted Mon January 23, 2023 09:37 AM
    Whats the prospect of a updated  IBM.EntityFrameworkCore package for EFcore 7 ?

    ------------------------------
    Torben Hørup
    ------------------------------


  • 2.  RE: dotnet 7 / ef core 7 ?

    Posted Tue January 24, 2023 02:09 AM

    And just for reference

    If you try to use current IBM.EntityFrameworkCore with EFcore 7 you get this stacktrace

    System.MissingMethodException: Method not found: 'Void CoreTypeMappingParameters..ctor(System.Type, Microsoft.EntityFrameworkCore.Storage.ValueConversion.ValueConverter, Microsoft.EntityFrameworkCore.ChangeTracking.ValueComparer, Microsoft.EntityFrameworkCore.ChangeTracking.ValueComparer, System.Func`3<Microsoft.EntityFrameworkCore.Metadata.IProperty,Microsoft.EntityFrameworkCore.Metadata.IEntityType,Microsoft.EntityFrameworkCore.ValueGeneration.ValueGenerator>)'.
       at IBM.EntityFrameworkCore.Storage.Internal.Db2StringTypeMapping..ctor(String storeType, Nullable`1 dbType, Boolean unicode, Nullable`1 size, Boolean fixedLength, Nullable`1 sqlDbType)
       at IBM.EntityFrameworkCore.Storage.Internal.Db2TypeMapper..ctor(TypeMappingSourceDependencies dependencies, RelationalTypeMappingSourceDependencies relationalDependencies)
       at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
       at System.Reflection.ConstructorInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr)
       at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(ServiceCallSite callSite, RuntimeResolverContext context)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(ServiceCallSite callSite, RuntimeResolverContext context)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(ServiceCallSite callSite, RuntimeResolverContext context)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScopeCache(ServiceCallSite callSite, RuntimeResolverContext context)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScopeCache(ServiceCallSite callSite, RuntimeResolverContext context)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.Resolve(ServiceCallSite callSite, ServiceProviderEngineScope scope)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.DynamicServiceProviderEngine.<>c__DisplayClass2_0.<RealizeService>b__0(ServiceProviderEngineScope scope)
       at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService(Type serviceType, ServiceProviderEngineScope serviceProviderEngineScope)
       at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetService[T](IServiceProvider provider)   at IBM.Extensions.DependencyInjection.Db2ServiceCollectionExtensions.<>c.<AddEntityFrameworkDb2>b__0_2(IServiceProvider p)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScopeCache(ServiceCallSite callSite, RuntimeResolverContext context)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScopeCache(ServiceCallSite callSite, RuntimeResolverContext context)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScopeCache(ServiceCallSite callSite, RuntimeResolverContext context)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScopeCache(ServiceCallSite callSite, RuntimeResolverContext context)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScopeCache(ServiceCallSite callSite, RuntimeResolverContext context)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScopeCache(ServiceCallSite callSite, RuntimeResolverContext context)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.Resolve(ServiceCallSite callSite, ServiceProviderEngineScope scope)
       at Microsoft.Extensions.DependencyInjection.ServiceLookup.DynamicServiceProviderEngine.<>c__DisplayClass2_0.<RealizeService>b__0(ServiceProviderEngineScope scope)
       at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService(Type serviceType, ServiceProviderEngineScope serviceProviderEngineScope)
       at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)
       at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService[T](IServiceProvider provider)
       at Microsoft.EntityFrameworkCore.DbContext.get_DbContextDependencies()
       at Microsoft.EntityFrameworkCore.DbContext.get_ContextServices()
       at Microsoft.EntityFrameworkCore.DbContext.get_InternalServiceProvider()
       at Microsoft.EntityFrameworkCore.DbContext.Microsoft.EntityFrameworkCore.Infrastructure.IInfrastructure<System.IServiceProvider>.get_Instance()
       at Microsoft.EntityFrameworkCore.Infrastructure.Internal.InfrastructureExtensions.GetService[TService](IInfrastructure`1 accessor)
       at Microsoft.EntityFrameworkCore.Infrastructure.AccessorExtensions.GetService[TService](IInfrastructure`1 accessor)
       at Microsoft.EntityFrameworkCore.Infrastructure.DatabaseFacade.get_Dependencies()
       at Microsoft.EntityFrameworkCore.Infrastructure.DatabaseFacade.Microsoft.EntityFrameworkCore.Storage.IDatabaseFacadeDependenciesAccessor.get_Dependencies()
       at Microsoft.EntityFrameworkCore.RelationalDatabaseFacadeExtensions.GetFacadeDependencies(DatabaseFacade databaseFacade)
       at Microsoft.EntityFrameworkCore.RelationalDatabaseFacadeExtensions.GetDbConnection(DatabaseFacade databaseFacade)


    ------------------------------
    Torben Hørup
    ------------------------------



  • 3.  RE: dotnet 7 / ef core 7 ?

    Posted Tue January 24, 2023 05:29 AM
    Hi Torben,
     we are working on this support and .NET 7 will be released first, followed by EF 7. At present we are targeting to release .NET 7 by February 2023 and EF by March 2023. However, this is not a final commitment and the dates can change slightly.

    Thanks and regards
    Vishwa

    ------------------------------
    Hosathota Vishwanatha
    ------------------------------



  • 4.  RE: dotnet 7 / ef core 7 ?

    Posted Wed January 25, 2023 09:28 AM
    Hello

    Will there be a beta release for EF 7 like for EF 6?
    EF 6 beta was already available on 12/17/2021, a month after the release.
    No we are behind schedule, when you release,  EF 8 is almost there.

    ------------------------------
    Wim Baens
    ------------------------------



  • 5.  RE: dotnet 7 / ef core 7 ?

    Posted Tue February 28, 2023 04:20 AM

    > At present we are targeting to release .NET 7 by February 2023
    So the .net 7 release comes today ? :P 



    ------------------------------
    Torben Hørup
    ------------------------------



  • 6.  RE: dotnet 7 / ef core 7 ?

    Posted Fri March 17, 2023 10:29 AM

    Hi Vishwa,

    Is the .NET 7 version almost available?  Thank you!



    ------------------------------
    James Hunt
    ------------------------------



  • 7.  RE: dotnet 7 / ef core 7 ?

    Posted Fri March 31, 2023 04:20 AM

    So now were at a bit more than 2 months after my original post. Both of the targeted release dates/periods you mentioned has now passed. But still no release, not even a beta - nor do we have any updates from any IBM employee.

    Frankly, this is quite disappointing - especially the lack of communication.



    ------------------------------
    Torben Hørup
    ------------------------------



  • 8.  RE: dotnet 7 / ef core 7 ?

    Posted Fri April 07, 2023 04:09 AM

    Hi Torben,
      I understand the impact of the delay and thanks for your patience on this. We are close to release and it may happen either next week or week after that. 

    Thanks
    Vishwa



    ------------------------------
    Hosathota Vishwanatha
    ------------------------------



  • 9.  RE: dotnet 7 / ef core 7 ?

    Posted Wed April 19, 2023 04:43 AM

    Hi Torben and James,
     today we have released the .NET 7 and EF Core 7 packages to NuGet. Please let us know of any feedback you have on the packages.

    Thanks
    Vishwa



    ------------------------------
    Hosathota Vishwanatha
    ------------------------------



  • 10.  RE: dotnet 7 / ef core 7 ?

    Posted Wed April 19, 2023 06:49 AM

    Hi 

    We have just tried the updated package and everything seems good - a huge thank you to you and the team behind this update.

    /Torben



    ------------------------------
    Torben Hørup
    ------------------------------



  • 11.  RE: dotnet 7 / ef core 7 ?

    Posted Fri May 05, 2023 10:10 AM

    Hi Vishwa,

    Thanks for getting this out. We are testing and everything looks good so far.

    I am curious if there are plans to start preparing for dotnet 8, which is targetted for Nov. My team is already looking at dotnet 8 (especially as it will be the LTS release).

    Regards,
    Cuinn.



    ------------------------------
    Cuinn Wylie
    ------------------------------



  • 12.  RE: dotnet 7 / ef core 7 ?

    Posted Mon April 03, 2023 07:54 AM

    Hi @Hosathota Vishwanatha 

    Can you let us know what the new timeline is on this release?  I need to provide information to our team on when the release will be.  An estimate would be better than nothing.  Thank you!



    ------------------------------
    James Hunt
    ------------------------------



  • 13.  RE: dotnet 7 / ef core 7 ?

    Posted Fri April 07, 2023 04:11 AM

    Hi James,
     as communicated to Torben, the release may happen by next week or week after that. We are waiting for certain approvals.

    Thanks and regards
    Vishwa



    ------------------------------
    Hosathota Vishwanatha
    ------------------------------



  • 14.  RE: dotnet 7 / ef core 7 ?

    Posted Mon April 03, 2023 03:52 AM

    Additional question from me.. Will be driver AOT compatibile ? 



    ------------------------------
    Krzysztof Duśko
    ------------------------------



  • 15.  RE: dotnet 7 / ef core 7 ?

    Posted Fri April 07, 2023 04:18 AM

    Hi Krzysztof,
     since we are dependent on native C libraries and use APIs such as LoadLibrary internally, we will not be able to make our driver as AOT compatible. MS has limitations on these scenarios.

    Thanks
    Vishwa



    ------------------------------
    Hosathota Vishwanatha
    ------------------------------



  • 16.  RE: dotnet 7 / ef core 7 ?

    Posted Thu April 20, 2023 03:30 AM

    Not that SLIB as standard libraries are iril, are supported by IBM infrastructures in modelling tools as rapid techniques are not binded by .scoc or scotch files as type 2 dbql.
    http://cryphosnegative.blogspot.com/



    ------------------------------
    KIN BUENO
    ------------------------------