I am currently developing Silverlight 4.0 and mainly by creating class libraries with TDD in regular C # (before SL), I can say that my current process is slower than I'm used to. (I think this can be said for any UI code compared to library classes, but here I think this is really a serious problem for me.)
I am wondering what methods can be recommended to improve SL performance.
I'm mostly worried about hard code testing (from my POV) - MVVM and UI - what can be done to improve performance here, I think maybe this is a way to use a small sandbox somehow and control / debug behavior outside the scope of the whole application, it’s pretty clear to me that I am running the entire application to check if the new dialog box is working correctly, this is not the fastest way, and I could improve performance if I had a way to check this dialog, for example, and there is probably in other ways that I cannot think of, this may also be a solution.
EDIT: 1) this is what I found useful, since TDD is now a project that allows you to run tests for consoles, so you do not need to run Silverlight tests in a browser and can integrate them into your LightHouse build process
2), found on the next page, it gives some idea of a possible approach that could be used to check:
http://fohjin.blogspot.com/2008/09/how-to-test-your-xaml-behavior- using.html
there is no magical beautiful way, and this one can be used, but to name all the controls, for example, it needs to work, which is not very good often
source
share