In n-tier, distributed applications, we have to decide which logic deploy where. Those deployments are all about installing components in specific places but, what are components exactly? What distinguishes a component with respect of a mere class?
Actually, as classes do, components take ownership of cohesive responsability but components are logical units from a physical perspective. In MS .NET terms, components are redistributable assemblies (.dll) of one or more classes
But, wait, it's not so easy: new considerations arise in this context
In this eighth webcast, Dr. Joe Hummel focuses on the design and creation of .NET components. He explains what component references are and how the .NET CLR deals with them via component metadata
With respect of security issues, Hummel offers some notions on Threat Modeling and how to avoid it via strong-named assemblies
About versioning, know the benefits of the .NET's Global Assembly Cache and how it says bye-bye to the Windows Registry (leaving behind the DLL Hell)
Finally some notions of pluggable components or, said in other words, what role play in .NET the elements configuration, configSections, sectionGroup and section? What role plays the applicationSettings element? Tired of being tired of never finishing to understand it?
So come on, join us again and let's watch together a new chapter of Dr Hummel's series "Architecting Smart Client applications"
Turning Tiers into Components