This book is an excellent reference for framework design guidelines; how much of it should one use when designing / implementing a system? Or should just relying on FxCop/SyleCop be enough? Any references to books, blogs, etc are appreciated.
+1
A:
This book is about creation of clear and robust API. Most applications usually have separate layers each of which exposes an API. Which means you typically should follow these guidelines unless you have a strong reason not to.
FxCop rules describe mostly implementation level issues. They could warn you about side-effects in your code or unpredicted behavior, but never about granularity or usefulness of your methods. So, FDG book and FxCop are overlapping but different guidelines.
Ihar Voitka
2009-07-29 18:24:10
Thanks. One of the reasons I asked is for example FDG says to avoid creating new exception types, which may not be the case for an application.
Otávio Décio
2009-07-29 18:28:20
If new exception type will add value comparing to reuse of one of the existing exceptions from BCL, then it is good reason.
Ihar Voitka
2009-07-29 18:55:48
+1
A:
Take a look at Patterns & Practices Application Architecture Guide 2.0. That is more geared toward "normal" application implementation.
JP Alioto
2009-07-29 18:28:52