Breeze Server for .NET 4.x - OData V2.0 ... will stop working when the deprecated endpoint is removed.

[Bronzato1]

Hi,

I have a legacy .Net Framework 4.8 application using Breeze.Server NuGet packages. This one is using OData v2. There is a dependency with Microsoft.Data.OData which is deprecated.

On the website of Microsoft they wrote: "There are no immediate symptoms, but code that uses this endpoint will stop working when the deprecated endpoint is removed. The original removal date was November 11, 2022. It was extended to April 30, 2023. We decided not to remove the service on April 30, 2023, to give people more time to transition their code to use the Web API. If you're still using this endpoint, you must prioritize transitioning your code to use the Web API so that you're prepared when the final removal date is announced. You should change any code that depends on the Organization Data Service (OData v2.0) to use the Dataverse Web API (OData v4.0) endpoint instead."

They did not communicate so far for the (new) final removal date.

I'm in the process of rewriting this .Net Framework application to .Net Core but it may take up to 1 year to rewrite it.

What should I think of it? Should I understand that the day OData v2 is no longer supported, the application will stop working? Because this web app is using Breeze for .Net 4.x which is only compatible with OData v2. What do you recommend to me?

Thanks.

[steveschmitt]

code that uses this endpoint will stop working when the deprecated endpoint is removed.

The legacy application will not stop working unless you update .NET to a version that no longer has OData v2. As long as you don't change the .NET framework or libraries, it should be fine.

The .NET Core versions of Breeze do not support OData. Microsoft's enthusiasm for OData decreased after v2, and we worried that they would stop supporting it altogether. So newer Breeze versions use a JSON protocol for both queries and results.

That said, the syntax and behavior of Breeze is similar across all versions, so converting that part of the application should be a... breeze.

[Bronzato1]

Thanks Steve for your quick answer of yesterday. Your response is intended to be reassuring.

You wrote:

The legacy application will not stop working unless you update .NET to a version that no longer has OData v2. As long as you don't change the .NET framework or libraries, it should be fine.

Am I to understand that even if Microsoft removes this package next month, applications that still depend on OData v2 (including Microsoft.Data.OData) will still work? This is the first time I've encountered this kind of problem.

The legacy application is based on Breeze to manage all data. As far as I know, I have no other alternatives than to rewrite everything in .Net Core.

I have submitted a ticket to Microsoft professional support and I hope to receive clarification in particular:
(1) when OData v2 will be officially retired?
(2) what will happen for applications still depending on this technology? (notably through Microsoft.Data.OData)

I will keep you informed of Microsoft's response.

[steveschmitt]

For your .NET Core app, you will want packages
Breeze.AspNetCore.NetCore
Breeze.Persistence.EFCore
The Breeze server-side syntax is basically the same, except that we call it a PersistenceManager instead of ContextProvider.

Our documentation is a bit out of date, but you can look at the Northwind sample application and the steps to get you started. The sample is .NET 5, but I recommend you use .NET 8. The steps are about the same.

[Bronzato1]

I got a response from Microsoft regarding the final depreciation for OData version 2.

The OData v2 libraries will continue to be available (i.e., will not be withdrawn in the foreseeable future) but not updates or security patches are currently released for V2 libraries.

[steveschmitt]

Good news, thanks.