You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Strictly speaking, an exporting member may produce unique values each time it is pulled from, so two "identical" imports may in fact be valuable to the consumer in getting two unique instances. However this is by far a very niche case, so an analyzer to catch what would commonly be a (minor) bug or at least a cosmetic anomaly may be useful.
My sense though is this is a low priority as it seems unlikely to result in a bug.
I found a MEF part today that imported the same object via two constructor parameters, but with different names.
The same is possible for
parameterproperty injection.While harmless, it's a little messy and may lead to confusion. An analyzer could detect this.
The text was updated successfully, but these errors were encountered: