.
Is this fixable, or can this only be solved when upgrading to v14 as no separate constructor seems to exists?
d
D_Inventor
12/06/2023, 8:23 AM
Heyo!! Usually if something is obsolete, there is an alternative available. You say that in this case, there is no alternative, so assuming that there is no alternative, you might be able to fix your issue by marking your own constructor as obsolete as well.
a
Ambert
12/06/2023, 9:22 AM
But that would create a new warning 😄
d
D_Inventor
12/06/2023, 9:25 AM
Interesting, I just tried it and marked a method as obsolete. There's no warning on the method itself, only on calls to that method. Do you explicitly call your constructor somewhere? I wouldn't expect warnings if you just register your type in dependency injection (unless you marked the whole type as obsolete)
a
Ambert
12/06/2023, 9:28 AM
Hmm, you're right
Ambert
12/06/2023, 9:28 AM
Would have to make note of the obsolete methods somewhere though