Having a deep knowledge of your toolset, when you start a new application from scratch, does not necessarily mean you are able to develop rapidly and effectively. The biggest problems, infact, do not come from the missing knowledge of a feature, that you can easily fill with a short search on the Internet, but from the grow of complexity of your application when you start putting things together without knowing exactly how you can better organize them to avoid the exponential increase of entropy. The first and much more important aspect is the architectural pattern, made of a set of classes that collaborate together, separating responsabilities between different actors in the UI layer. Be aware that I'm not speaking about the organization of the application tiers, usually separated in UI, Business Logic and Data but about a separation which is completely internal at the UI layer.


I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.

Stay tuned to my blogtwitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.


This article is related to

C#,.NET,Architect,Intermediate,XAML,.Net,Articles,Computer Tutorials, Web Development, Web, HTML, HTML5