- ago
I am developing a custom broker extension.

The Configurable class (from which the BrokerBase class is derived) calls the virtual method "LoadConfig" from its constructor, which is considered a bad coding practice (https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca2214).

I am generating the broker's "Name" property dynamically using some instance properties. Before I can save/access these instance properties, the Name property is accessed from the LoadConfig method.

This can be considered a bug - Calling an overridable method/property before giving the derived class a chance to initialize/implement the override.

I can work this around, but I am bringing it to the dev team's notice.
0
63
1 Replies

Reply

Bookmark

Sort
Glitch8
 ( 6.41% )
- ago
#1
Glad you could work around that! This won’t be changed for WL8 but will keep it in mind for the next go around.
1

Reply

Bookmark

Sort