In the old MS123 Visualizers library there was a file called PerformanceEngine.cs
Has this moved or is it available somewhere else. I know that the whole RunDonor strategy had a breaking change a while back.
Thx
Size:
Color:
The internal and unsupported PerformanceEngine class is still there in the WealthLab.Visualizers.MS123 namespace, rewritten from scratch and delivering the performance metrics to all members of MS123 Visualizers. However, it has never included "runDonor" -- that's the prerogative of Community Components. As it's not entirely clear to me, could you clarify what you're after?
Size:
Color:
Size:
Color:
I am getting messages about Community Components is "obsolete" despite having updated all extensions
Size:
Color:
QUOTE:
I am getting messages about Community Components is "obsolete" despite having updated all extensions
This is a heads-up, and it's there on purpose. With the advent of
extension methods - a C# 3.0 feature - I consider the majority of pre-2013.05 legacy syntax "obsolete". The Wiki examples have been updated to reflect the new usage patterns, but everyone can continue running their legacy code as nothing happened. Through wrappers to new extension methods, the old syntax stays supported forever (
exception: new additions will never be backported). Since C.Components is a utility library, the need to create classes has been minimized: we're using static classes/methods wherever possible, and the new extension method syntax makes it even easier, more comfortable and terse.
QUOTE:
I had this running before but not since the "breaking change" described here
Starting from v2012.11, MS123 Visualizers include an own 'Utility' class - perhaps this is the source of confusion with 'Community.Components.Utility' that you were using. Posts #16 and #17 by your link contain everything one needs to know to adjust their code to the breaking change in the unsupported internal class.
Size:
Color:
Okay, perhaps you can help me out one more time. The following code works just fine
CODE:
Please log in to see this code.
If I try to replace the last line with
CODE:
Please log in to see this code.
which used to work. I get the message about the Utility is obsolete. I'm having difficulty figuring out what's going wrong. I seem to be referencing the right things as per your post above.
Appreciate the help. It is rather important to me
Size:
Color:
Current revision of the unsupported internal PerformanceEngine class has no public variable "win_pct". Are you looking for pe.PctWinners?
Size:
Color:
Yes! as well as others. I believe the AvgProftWinPct has changed as well
I'd like to know all the public properties. I thought I had found them but it seems I am looking at the wrong places.
Can you point me toward the zip file to download.
Many thanks
Size:
Color:
Version 2013.01 seems to be current.
The zip file version is 2012.07 on the wiki site
I use the built in c# editor in WL. Often I can see the properties for example, in the code above, if I write x = sp. (after the dot is typed, the available methods and properties appear. Not so with pe "dot"
Am I doing something wrong
Size:
Color:
The demo solution is stuck forever at 2012.07 after the total rewrite of the library. It was decided that the old version is perfectly enough for the demo purposes and therefore will not be updated.
At the risk of repeating, the PerformanceEngine class is unsupported and internal. So you're completely on your own with it. No public and/or other properties will ever be documented. Feel free to explore its properties using Visual Studio's Object Browser and similar tools. Please look for any assistance on Visual Studio forums and by studying your Visual Studio manual.
Good luck with your venture, and I really appreciate your understanding that you're using an undocumented method with all that that implies.
Size:
Color:
Eugene,
You mentioned above that the wiki was updated with the new supported usage patterns. Could you point me in the right direction in wiki to view these as there is no time stamp with regard to updates in the wiki. Thanks ahead of time for your help.
Size:
Color:
Size:
Color:
Thanks Eugene.
Size:
Color:
Size:
Color:
A slowdown on "trading the equity curve" using that code is expected as per "Notes and Limitations". There's nothing to fix because the KB article code is not broken.
Size:
Color: