Design Patterns
-
Chris Austin wrote:
You are about a decade behind.
More like two decades! :) Any old-timer OOPSLA members around? /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
I have been onto some project totally off the hook lately Say what are some good resource for design patterns for .NET?
Omit Needless Words - Strunk, William, Jr.
Like tricks, Vista? Daily Tricks Vista Gadget, Trick of Mind
-
Design Patterns in C# is a good book. My only complaint is that there are lots of errors, most of which are very sneaky, so you have to be paying attention. For example, I was just reading the chapter on the Composite pattern and one of the class names was typo'd as "MachineComponent" when it should have been "MachineComposite". I've found quite a few of those, and I'm considering looking up the errata website for the book and noting them all in the book. I really enjoy reading about patterns. They come in handy especially when writing extensible frameworks, custom controls, etc. Some are really common, like factory method. Others, It really makes me miss writing manufacturing applications, because that's where they really come in handy. Now that I'm writing mostly business web apps with ASP.NET, I find myself reaching for Martin Fowler's Patterns of Enterprise Application Architecture much more often than GoF. Jordan
Jordan Marr wrote:
Design Patterns in C#
thanks for the suggestion, I will check that
Omit Needless Words - Strunk, William, Jr.
Like tricks, Vista? Daily Tricks Vista Gadget, Trick of Mind
-
I have been onto some project totally off the hook lately Say what are some good resource for design patterns for .NET?
Omit Needless Words - Strunk, William, Jr.
Like tricks, Vista? Daily Tricks Vista Gadget, Trick of Mind
Personally, all of the .net specific books I looked at sucked several years ago. I'd recommend just studying the concepts of patterns and books that attempt to be language neutral.
A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. - -Lazarus Long
-
I have been onto some project totally off the hook lately Say what are some good resource for design patterns for .NET?
Omit Needless Words - Strunk, William, Jr.
Like tricks, Vista? Daily Tricks Vista Gadget, Trick of Mind
Sorry, I don't know of any book specific to .NET. Design patterns are language independent, although admittedly easier to implement in object oriented languages. I have a well thumbed copy of GOF on my bookshelf but rarely refer to it these days. Most of the patterns I use are second nature I guess... /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
Lately I have seen all the microsoft .net community have become crazy about design patterns (Gang of Four). After looking closely I was surprised how many of them i have already used in one way or the other. Well ! The design pattern book by gamma et al is sleep inducing , I got the "Head First Design Pattern" which was meant for Java programmer but is AWESOME and applies equally to .net. Read the whole book in 2 days Was wondering any other good book out there with respect to .net ? Anybody feel patterns are the new hype ?
Omit Needless Words - Strunk, William, Jr.
Like tricks, Vista? Daily Tricks Vista Gadget, Trick of Mind
Quartz. wrote:
Anybody feel patterns are the new hype ?
Design patterns are common approaches for implementing higher level abstractions in languages that do not provide direct support for them. For example, if a design patterns book were written with the C language as its primary target, you would find patterns in it called "Polymorphism" or "Inheritance," with descriptions of how to implement those features using C. When a language evolves to provide support for a design pattern, it ceases to be a pattern and becomes a feature through which you can more easily realize a design. I don't think much about the Observer design pattern when using C# because it gives me delegates and events. On the other hand, when I write in C++ and need a notification system, I find myself writing the needed infrastructure from scratch. The Observer design pattern informs me on how this can be done. You don't hear about Visitor much in languages that provide double dispatching. Design patterns are a stepping stone in the evolution towards programming languages that provide the means for realizing higher level abstractions. They're important because they show us what we need to make our lives easier.
-
I may have that book, does it talk about networking patterns and so on ? Ludicrious.
Christian Graus Please read this if you don't understand the answer I've given you "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it ) ( spaces added for the benefit of people running at < 1280x1024 )
Christian Graus wrote:
about networking patterns and so on
ya somethings like that totally clueless
Omit Needless Words - Strunk, William, Jr.
Like tricks, Vista? Daily Tricks Vista Gadget, Trick of Mind
-
I have been onto some project totally off the hook lately Say what are some good resource for design patterns for .NET?
Omit Needless Words - Strunk, William, Jr.
Like tricks, Vista? Daily Tricks Vista Gadget, Trick of Mind
I suggest Design Patterns by Christopher G. Lasater. He rewrites Gang of Four's book in a digestible way. It has also C# examples and clear class diagrams. I have read also Head First on Design Patterns but I didn't like it, actually much more fluff than stuff.
-
I suggest Design Patterns by Christopher G. Lasater. He rewrites Gang of Four's book in a digestible way. It has also C# examples and clear class diagrams. I have read also Head First on Design Patterns but I didn't like it, actually much more fluff than stuff.
thanks for your message, much appreciated
Omit Needless Words - Strunk, William, Jr.
Like tricks, Vista? Daily Tricks Vista Gadget, Trick of Mind
-
I suggest Design Patterns by Christopher G. Lasater. He rewrites Gang of Four's book in a digestible way. It has also C# examples and clear class diagrams. I have read also Head First on Design Patterns but I didn't like it, actually much more fluff than stuff.
AugustoS wrote:
actually much more fluff than stuff
kind of hit the spot there
Omit Needless Words - Strunk, William, Jr.
Like tricks, Vista? Daily Tricks Vista Gadget, Trick of Mind
-
Quartz. wrote:
Anybody feel patterns are the new hype ?
Design patterns are common approaches for implementing higher level abstractions in languages that do not provide direct support for them. For example, if a design patterns book were written with the C language as its primary target, you would find patterns in it called "Polymorphism" or "Inheritance," with descriptions of how to implement those features using C. When a language evolves to provide support for a design pattern, it ceases to be a pattern and becomes a feature through which you can more easily realize a design. I don't think much about the Observer design pattern when using C# because it gives me delegates and events. On the other hand, when I write in C++ and need a notification system, I find myself writing the needed infrastructure from scratch. The Observer design pattern informs me on how this can be done. You don't hear about Visitor much in languages that provide double dispatching. Design patterns are a stepping stone in the evolution towards programming languages that provide the means for realizing higher level abstractions. They're important because they show us what we need to make our lives easier.
hi guyz, find the plenty of available patterns at www.dofactory.com thanks, Pashi
-
Lately I have seen all the microsoft .net community have become crazy about design patterns (Gang of Four). After looking closely I was surprised how many of them i have already used in one way or the other. Well ! The design pattern book by gamma et al is sleep inducing , I got the "Head First Design Pattern" which was meant for Java programmer but is AWESOME and applies equally to .net. Read the whole book in 2 days Was wondering any other good book out there with respect to .net ? Anybody feel patterns are the new hype ?
Omit Needless Words - Strunk, William, Jr.
Like tricks, Vista? Daily Tricks Vista Gadget, Trick of Mind
Quartz. wrote:
The design pattern book by gamma et al is sleep inducing
That was my first reaction to the book too. But give it another go, once you get over the formal writing style, the content is actually pretty good, and by the time you've gone through a couple of the patterns, you start to get benefit from the writing style. Well, at least I did anyway. It helped me to abstract the concepts. Just my two cents...
Quartz. wrote:
I got the "Head First Design Pattern"
Cheers for the heads up - I'll stick that one on my ever growing "to read" list
- Dy
-
Lately I have seen all the microsoft .net community have become crazy about design patterns (Gang of Four). After looking closely I was surprised how many of them i have already used in one way or the other. Well ! The design pattern book by gamma et al is sleep inducing , I got the "Head First Design Pattern" which was meant for Java programmer but is AWESOME and applies equally to .net. Read the whole book in 2 days Was wondering any other good book out there with respect to .net ? Anybody feel patterns are the new hype ?
Omit Needless Words - Strunk, William, Jr.
Like tricks, Vista? Daily Tricks Vista Gadget, Trick of Mind
Patterns have been around for far longer than computers. Why reinvent the wheel when there is already a pattern available The expression keystone arch was used for years to describe a particular pattern for building a bridge. People will always need to be able to describe a commonly used aggregation of parts by a recognised word to get the job done, otherwise even simple tasks would take ages to perform. I think it just took a length of time before people realised what the commonly used patterns were in the CS field and then a bit longer for someone to write it down and even longer for it to become a widely accepted concept.