Thanks for the example, very much appreciated. Looks to me like it's just the VS debugger slowing it down.
If you ctrl-F5 then it's instant - at this point I really wish I could explain why the WPF debugger is so slow, and if it's something about how we're doing things - we'll have to profile the debugger for the next release.
If it's going to be too painful to use, please let me know and I'll see if we can bring forward the profiling, it's possible that there's just some API call that bottlenecks the WPF runtime debugger.... so it might be an easy fix.
Best
Jim
-your feedback is helpful to other users, thank you!Evaluation Downloads-your feedback is helpful to other users, thank you!
