Asp.Net core

[Pival81]

How am I meant to use this with an aspnet core web api project?
Like, I want to return my objects in my controllers with the extendedxmlserializer with my custom options instead of the default one.
I saw there's a support package, but it's for an old version and doesn't work.

[WojciechNagorski]

I can take care of it. sob., 5 gru 2020, 12:45 użytkownik Valerio Pizzi <[email protected]> napisał:

…

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#490>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEEH5D4U5JD3JT7VM2RRUKTSTIMMBANCNFSM4UOPZEXA> .

[Mike-E-angelo]

I was thinking of this issue, and one thing to be aware of is that there have been quite a few changes since v1. Most notably, we use our own custom namespace and attributes that other XML serializers will not recognize and/or handle in the same way.

If the consumer/client of your ASP.NET Core API is also using ExtendedXmlSerializer (yay 😁), this is not an issue. However, if they are not, then this is something to be aware of and I am not sure how viable this scenario is anymore.

[Mike-E-angelo]

Going once, going twice. :) Checking in on this issue. Has there been any activity around it? Since it's been a couple of months now I am apt to stale it if no work is being done around it (or is planned to do so). Please feel free to add any additional comments here. Otherwise, I will give it some time and close if no further activity has been performed and/or is planned.

[Mike-E-angelo]

Looks like there is no activity on this issue. Unfortunately with my own time constraints I cannot look into this at depth. If work is done on this at a later time please comment on this thread and we can take a further look into it. Closing for now.