Feeds

Framework Design Guidelines

Conventions, Idioms and Patterns for Reusable .NET Libraries

Providing a secure and efficient Helpdesk

Book review While Framework Design Guidelines: Conventions, Idioms and Patterns for Reusable.NET Libraries hardly rolls off the tongue, it has the obvious virtue of faithfully describing the contents. And while the subject of coding and design guidelines might not get the juices running in the same way as a tome on the latest scripting language or a fancy new web technology, it’s also true that a solid grasp of the subject is likely to be of more long term value to a developer.

Framework Design Guidelines book cover By frameworks the authors mean collections of components which are designed for reuse – in other words libraries, middleware components, toolkits and the like. In contrast to standalone applications, these frameworks are defined by their APIs, the public interface through which other developers can make use of them. And the prime example the authors refer to is, of course, Microsoft’s .NET Framework; as they make clear, the guidelines in this book are those developed, tested and refined by the development of .NET.

The book covers both design principles and more mundane issues such as coding standards, naming conventions and so on. The first couple of chapters focus on design and philosophy, describing both the desirable attributes of a well-designed framework (simplicity, consistency, built with evolution in mind), and some fundamental guiding principles (layered architecture, self-documenting object models). Design principles are also revisited in a later chapter on common design patterns, such as the use of factory methods for object creation.

The nuts and bolts of coding are not neglected. Naming guidelines include capitalisation rules, names for classes, interfaces, structs, assemblies, name spaces, and much more. On first sight there appear to be endless layers of detail – how hard can it be to come up with rules on how to capitalise identifiers? However, it’s a horrible fact of life that depending on common sense and good luck just isn’t enough. And once an API has been published, all kinds of inconsistencies and exceptions become glaringly obvious to your users, who’ll take no end of pleasure in pointing them out.

Of course, this isn’t the first book to cover this sort of ground. Steve McConnell’s excellent ”Code Complete” (reviewed here), has plenty to say on coding and naming standards. And Joshua Bloch’s ”Effective Java” (reviewed here), covers design object oriented design principles. Interestingly, both books are name checked and are clear influences. While the .NET focus is evident, it has to be said that the principles and guidelines are independent of language and, to a very large extent, independent of platform. So, not only is this a book that applies to all of the .NET languages rather than just C#, most of it makes good sense for Java, Python and the rest.

Given the subject matter, the writing’s on the dry side. But the solid technical content is leavened with comments and asides from a number of experienced developers and architects.

Framework Design Guidelines: Conventions, Idioms and Patterns for Reusable .NET Libraries

Verdict: All in all, this is an impressive and useful book that is easy to recommend.

Author: Krzysztof Cwalina and Brad Abrams

Publisher: Addison Wesley

ISBN: 0321246756

Media: Book

List Price: £28.99

Reg price: £23.19

Secure remote control for conventional and virtual desktops

More from The Register

next story
Not appy with your Chromebook? Well now it can run Android apps
Google offers beta of tricky OS-inside-OS tech
New 'Cosmos' browser surfs the net by TXT alone
No data plan? No WiFi? No worries ... except sluggish download speed
Greater dev access to iOS 8 will put us AT RISK from HACKERS
Knocking holes in Apple's walled garden could backfire, says securo-chap
NHS grows a NoSQL backbone and rips out its Oracle Spine
Open source? In the government? Ha ha! What, wait ...?
Google extends app refund window to two hours
You now have 120 minutes to finish that game instead of 15
Intel: Hey, enterprises, drop everything and DO HADOOP
Big Data analytics projected to run on more servers than any other app
prev story

Whitepapers

Secure remote control for conventional and virtual desktops
Balancing user privacy and privileged access, in accordance with compliance frameworks and legislation. Evaluating any potential remote control choice.
Saudi Petroleum chooses Tegile storage solution
A storage solution that addresses company growth and performance for business-critical applications of caseware archive and search along with other key operational systems.
High Performance for All
While HPC is not new, it has traditionally been seen as a specialist area – is it now geared up to meet more mainstream requirements?
Security for virtualized datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.
Providing a secure and efficient Helpdesk
A single remote control platform for user support is be key to providing an efficient helpdesk. Retain full control over the way in which screen and keystroke data is transmitted.