.NET 6 Support

[Prinsn]

I previously was part of an upgrade of a system moving from the breeze labs version of breeze js to the "breeze 2" and had some help here with debugging some things.

Unfortunately, after all was said and done, Azure's complete drop of the ball on supporting .NET 5 required a full rollback.

Now that .NET 6 is out, and Azure appears to have corrected this issue, we were looking at having it another go.

However, I'm currently finding it difficult to navigate the documentation to find any intention for .NET 6 support at http://breeze.github.io/doc-net/breeze-server-core

So this is sort of an ETA inquiry as much as it is a request for packages to be published that are compatible with .NET and EF Core 6 (assuming they aren't already, this is a research step)

[jtraband]

We absolutely plan to support .NET 6 and EF Core 6 once things have stabilized. We also want to wait for SqlServer to fully support EF Core 6, which I don't believe it does yet. My guess is that we should have support for both in Breeze within the next 3-4 months.

[Prinsn]

Noted, thanks.

Is that a response to .NET 5? The package for that was available very soon in relation.

On Tue, Nov 30, 2021, 6:45 PM jtraband @.***> wrote:

We absolutely plan to support .NET 6 and EF Core 6 once things have stabilized. We also want to wait for SqlServer to fully support EF Core 6, which I don't believe it does yet. My guess is that we should have support for both in Breeze within the next 3-4 months.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Breeze/breeze.server.net/issues/128#issuecomment-983129472, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAYR7G3EXGJSQKOUOIS7JS3UOVO23ANCNFSM5JCIPKEQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[christianacca]

If I try and use .net 6 + EF Core 5 now, will that likely still work in-lieu of "full" breeze support for EF Core 6?

[jtraband]

Working on .NET 6 version now. Probably available with a week or so.

[christianacca]

Nice one

[jtraband]

Ok, we just released .NET 6/EF Core 6 versions of all of the Breeze libraries.

This consists of version 6.0.1 of Breeze.Core, Breeze.Persistence, Breeze.Persistence.EFCore, Breeze.AspNetCore.NetCore

[christianacca]

Great. Perfect timing for me :-)

On Wed, 12 Jan 2022, 20:23 jtraband, @.***> wrote:

Ok, we just released .NET 6/EF Core 6 versions of all of the Breeze libraries.

This consists of version 6.0.1 of Breeze.Core, Breeze.Persistence, Breeze.Persistence.EFCore, Breeze.AspNetCore.NetCore

— Reply to this email directly, view it on GitHub https://github.com/Breeze/breeze.server.net/issues/128#issuecomment-1011420129, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGYOPUH4QGTZER2S3JCS2LUVXPKLANCNFSM5JCIPKEQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you commented.Message ID: <Breeze/breeze. @.***>

[Prinsn]

Currently getting

Uncaught Error: Uncaught (in promise): Error: Unable to locate a registered object by the name: JsonResultsAdapter.webApi_default
Error: Unable to locate a registered object by the name: JsonResultsAdapter.webApi_default
    at BreezeConfig._fetchObject (breeze-client.js:1594:1)

and uncertain how to address.

The only mention of the JsonResultsAdapter appears to be from http://breeze.github.io/doc-net/webapi-routing-4x and our current configuration has worked up till now

[Prinsn]

Leaving above to hopefully help anyone else that gets here:

Problem was a skipped step in the client project regarding

Then, in your constructor function (for your module or Entity Manager Provider):

constructor(http: HttpClient) {
    // the order is important
    ModelLibraryBackingStoreAdapter.register();
    UriBuilderODataAdapter.register();
    AjaxHttpClientAdapter.register(http);
    DataServiceWebApiAdapter.register();
}

because we didn't use these before, so "replacing them" didn't make sense