Nick Hustak

I'm glad to see this getting some attention. It's a serious issue in an otherwise extremely nice API.

Just keeping this thread alive. It's really time to delivery this.

@lxalln I 100% concur with you on this. I am extremely concerned about the lack of movement here.

Need some feedback on this. Need this ASAP. What do you expect us to do?

I called support on this and basically got a non-answer. It's incredibly frustrating that they don't see this as a priority especially when it's fairly simple to get it working.

@cdwiegand Few tweaks and you can make the current library compile under standard. I've been using it for a while now. They apparently are no longer going to support .NET...

Hah...good luck with that. It's amazing, isn't it? On Wed, Aug 3, 2022 at 11:42 AM Jeff Mikan ***@***.***> wrote: > Any update on trying a 4 year old beta...

It's a joke. Still no support. In the meantime, they've released 2.x which is a huge set of breaking changes.

I've been using it in 11 since it came out. Maybe describe what issue you are seeing?

Ah, ok I see it's not listed on the versions. I have had no issues with it in Angular 11.