5 of its namespaces (,, ,, ) and the class map to the desktop's PresentationFramework.dll System.ComponentModel comes from System.dll (! again) and is basically the BackgroundWorker implementation. System.Net namespace with WebClient plus 6 related classes comes from the desktop's System.dll (!) Its namespaces come from various v2.0 and v3.0 desktop assemblies as listed below (and it is in my opinion a prime candidate for refactoring): You can think of it as the brick that gives Silverlight its WPF UI. is yet another Silverlight assembly with no direct counterpart in the full framework, but with tons of stuff inside (as evidenced by its size on disc and by the 21 namespaces!) that makes it the 2nd largest assembly. Following from Part 1, Part 2 and Part 3, in this last part of the exploration I'll focus on the UI layer and I'll have even more of a statistical hat on.ฤก1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |