Microsoft Silverlight Books

BFM - Big Fing Mess

Why am I using this pattern? Book shows the convoluted solution but not the problem. Before/After code would have been very illuminating. Code examples run on and on. Wiki pages on the individual patterns have very short and to the point c# examples so I used those instead. Not too much verbiage in there actually describing why you would use the pattern. Relies too much on UML diagrams.

D. Dillard
06 August, 2010

Design patterns book for reference?

I have to admit that the author had a good layout for this book. Each pattern, the author explains clearly
the roll of the pattern, illustration sample, design, implementation, and usage. Since the title of this
book specifically said "C# 3.0 design patterns", the author also introducing C# features where needed.
I chose this book because I expected to see how new C# 3.0 features brought in each pattern. However, nothing much in this book.


If you are looking for a good tutorial to learn patterns for the first time, then avoid this book. You may
be overwhelmed by many unclear illustrations. It is going to be hard for you to keep these patterns in your memory. I am familiar with design patterns. I had to skip reading many illustrations sections to avoid confusing. Also I don't really like using the same sample for more than one pattern. So, it is just one of the design pattern book, and not really the one that I want to keep in my bookcase.



Vu Tran
20 April, 2010

Not quite good enough

Design Patterns is probably one of those topics where multiple view points are beneficial. I made it all the way to the next to last pattern described - the interpreter - before I decided that my grasp of the topic would be improved by another book, rather than a reread of this book. I am a bit fearful of the original GOF design patterns book, so I have ordered the Head First book.

Sometimes the code examples do not appear to conform to the UML model, so I was confused about the role of any partucular class or method.
The 1 page explanation of UML was insufficient with respect to its use throughout the book. Maybe I'll also get a UML book.
The C# features side bars could be dispensed with; anybody reading this book should already have another book containing this material.
Sometimes the author employs some new vocabulary deserving further explanation, but none is provided.
The author's website for this book is not uptodate. The errata only mentions errors up through page 66 (of 280+ pages) and even that is not complete. The index could be a lot better.
The author does not respond to (pleasantly worded) email queries, so you are on your own.

T. Gabriel
14 March, 2010

Not quit good enough

Design Patterns is probably one of those topics where multiple view points are beneficial. I made it all the way to the next to last pattern described - the interpreter - before I decided that my grasp of the topic would be improved by another book, rather than a reread of this book. I am a bit fearful of the original GOF design patterns book, so I have ordered the Head First book.

Sometimes the code examples do not appear to conform to the UML model, so I was confused about the role of any partucular class or method.
The 1 page explanation of UML was insufficient with respect to its use throughout the book. Maybe I'll also get a UML book.
The C# features side bars could be dispensed with; anybody reading this book should already have another book containing this material.
Sometimes the author employs some new vocabulary deserving further explanation, but none is provided.
The author's website for this book is not uptodate. The errata only mentions errors up through page 66 (of 280+ pages) and even that is not complete. The index could be a lot better.
The author does not respond to (pleasantly worded) email queries, so you are on your own.

T. Gabriel
14 March, 2010

Not quite good enough

Design Patterns is probably one of those topics where multiple view points are beneficial. I made it all the way to the next to last pattern described - the interpreter - before I decided that my grasp of the topic would be improved by another book, rather than a reread of this book. I am a bit fearful of the original GOF design patterns book, so I have ordered the Head First book.

Sometimes the code examples do not appear to conform to the UML model, so I was confused about the role of any partucular class or method.
The 1 page explanation of UML was insufficient with respect to its use throughout the book. Maybe I'll also get a UML book.
The C# features side bars could be dispensed with; anybody reading this book should already have another book containing this material.
Sometimes the author employs some new vocabulary deserving further explanation, but none is provided.
The author's website for this book is not uptodate. The errata only mentions errors up through page 66 (of 280+ pages) and even that is not complete. The index could be a lot better.
The author does not respond to (pleasantly worded) email queries, so you are on your own.

T. Gabriel
14 March, 2010

Not quite good enough

Design Patterns is probably one of those topics where multiple view points are beneficial. I made it all the way to the next to last pattern described - the interpreter - before I decided that my grasp of the topic would be improved by another book, rather than a reread of this book. I am a bit fearful of the original GOF design patterns book, so I have ordered the Head First book.

Sometimes the code examples do not appear to conform to the UML model, so I was confused about the role of any partucular class or method.
The 1 page explanation of UML was insufficient with respect to its use throughout the book. Maybe I'll also get a UML book.
The C# features side bars could be dispensed with; anybody reading this book should already have another book containing this material.
Sometimes the author employs some new vocabulary deserving further explanation, but none is provided.
The author's website for this book is not uptodate. The errata only mentions errors up through page 66 (of 280+ pages) and even that is not complete. The index could be a lot better.
The author does not respond to (pleasantly worded) email queries, so you are on your own.

T. Gabriel
14 March, 2010

Not quite good enough

Design Patterns is probably one of those topics where multiple view points are beneficial. I made it all the way to the next to last pattern described - the interpreter - before I decided that my grasp of the topic would be improved by another book, rather than a reread of this book. I am a bit fearful of the original GOF design patterns book, so I have ordered the Head First book.

Sometimes the code examples do not appear to conform to the UML model, so I was confused about the role of any partucular class or method.
The 1 page explanation of UML was insufficient with respect to its use throughout the book. Maybe I'll also get a UML book.
The C# features side bars could be dispensed with; anybody reading this book should already have another book containing this material.
Sometimes the author employs some new vocabulary deserving further explanation, but none is provided.
The author's website for this book is not uptodate. The errata only mentions errors up through page 66 (of 280+ pages) and even that is not complete. The index could be a lot better.
The author does not respond to (pleasantly worded) email queries, so you are on your own.

T. Gabriel
14 March, 2010

Not quite good enough

Design Patterns is probably one of those topics where multiple view points are beneficial. I made it all the way to the next to last pattern described - the interpreter - before I decided that my grasp of the topic would be improved by another book, rather than a reread of this book. I am a bit fearful of the original GOF design patterns book, so I have ordered the Head First book.

Sometimes the code examples do not appear to conform to the UML model, so I was confused about the role of any partucular class or method.
The 1 page explanation of UML was insufficient with respect to its use throughout the book. Maybe I'll also get a UML book.
The C# features side bars could be dispensed with; anybody reading this book should already have another book containing this material.
Sometimes the author employs some new vocabulary deserving further explanation, but none is provided.
The author's website for this book is not uptodate. The errata only mentions errors up through page 66 (of 280+ pages) and even that is not complete. The index could be a lot better.
The author does not respond to (pleasantly worded) email queries, so you are on your own.

T. Gabriel
14 March, 2010

Not quite good enough

Design Patterns is probably one of those topics where multiple view points are beneficial. I made it all the way to the next to last pattern described - the interpreter - before I decided that my grasp of the topic would be improved by another book, rather than a reread of this book. I am a bit fearful of the original GOF design patterns book, so I have ordered the Head First book.

Sometimes the code examples do not appear to conform to the UML model, so I was confused about the role of any partucular class or method.
The 1 page explanation of UML was insufficient with respect to its use throughout the book. Maybe I'll also get a UML book.
The C# features side bars could be dispensed with; anybody reading this book should already have another book containing this material.
Sometimes the author employs some new vocabulary deserving further explanation, but none is provided.
The author's website for this book is not uptodate. The errata only mentions errors up through page 66 (of 280+ pages) and even that is not complete. The index could be a lot better.
The author does not respond to (pleasantly worded) email queries, so you are on your own.

T. Gabriel
14 March, 2010

Not quite good enough

Design Patterns is probably one of those topics where multiple view points are beneficial. I made it all the way to the next to last pattern described - the interpreter - before I decided that my grasp of the topic would be improved by another book, rather than a reread of this book. I am a bit fearful of the original GOF design patterns book, so I have ordered the Head First book.

Sometimes the code examples do not appear to conform to the UML model, so I was confused about the role of any partucular class or method.
The 1 page explanation of UML was insufficient with respect to its use throughout the book. Maybe I'll also get a UML book.
The C# features side bars could be dispensed with; anybody reading this book should already have another book containing this material.
Sometimes the author employs some new vocabulary deserving further explanation, but none is provided.
The author's website for this book is not uptodate. The errata only mentions errors up through page 66 (of 280+ pages) and even that is not complete. The index could be a lot better.
The author does not respond to (pleasantly worded) email queries, so you are on your own.

T. Gabriel
14 March, 2010

Not quite good enough

Design Patterns is probably one of those topics where multiple view points are beneficial. I made it all the way to the next to last pattern described - the interpreter - before I decided that my grasp of the topic would be improved by another book, rather than a reread of this book. I am a bit fearful of the original GOF design patterns book, so I have ordered the Head First book.

Sometimes the code examples do not appear to conform to the UML model, so I was confused about the role of any partucular class or method.
The 1 page explanation of UML was insufficient with respect to its use throughout the book. Maybe I'll also get a UML book.
The C# features side bars could be dispensed with; anybody reading this book should already have another book containing this material.
Sometimes the author employs some new vocabulary deserving further explanation, but none is provided.
The author's website for this book is not uptodate. The errata only mentions errors up through page 66 (of 280+ pages) and even that is not complete. The index could be a lot better.
The author does not respond to (pleasantly worded) email queries, so you are on your own.

T. Gabriel
14 March, 2010

Should have listened to other reviewers

This is my first ever Amazon review. After buying this book and reading almost the complete thing (1 chapter shy of the end) I am incredibly disappointed. There is barely any explanation as to how and why the individual patterns are used. Instead the author focuses on examples, which could have been a good approach except that her choices are horrible. The author sticks with (pretty much) one example that makes no sense unless you are 13 (I love Facebook as much as everyone else, but I don't see it as a CLEAR example of any of the patterns). Despite others negative reviews (very similar to my own) I purchased the book because I am a big fan of the O'Reilly books. Don't make the same mistake I did.

NONE
09 March, 2010

Should have listened to other reviewers

This is my first ever Amazon review. After buying this book and reading almost the complete thing (1 chapter shy of the end) I am incredibly disappointed. There is barely any explanation as to how and why the individual patterns are used. Instead the author focuses on examples, which could have been a good approach except that her choices are horrible. The author sticks with (pretty much) one example that makes no sense unless you are 13 (I love Facebook as much as everyone else, but I don't see it as a CLEAR example of any of the patterns). Despite others negative reviews (very similar to my own) I purchased the book because I am a big fan of the O'Reilly books. Don't make the same mistake I did.

NONE
09 March, 2010

Should have listened to other reviewers

This is my first ever Amazon review. After buying this book and reading almost the complete thing (1 chapter shy of the end) I am incredibly disappointed. There is barely any explanation as to how and why the individual patterns are used. Instead the author focuses on examples, which could have been a good approach except that her choices are horrible. The author sticks with (pretty much) one example that makes no sense unless you are 13 (I love Facebook as much as everyone else, but I don't see it as a CLEAR example of any of the patterns). Despite others negative reviews (very similar to my own) I purchased the book because I am a big fan of the O'Reilly books. Don't make the same mistake I did.

NONE
09 March, 2010

Should have listened to other reviewers

This is my first ever Amazon review. After buying this book and reading almost the complete thing (1 chapter shy of the end) I am incredibly disappointed. There is barely any explanation as to how and why the individual patterns are used. Instead the author focuses on examples, which could have been a good approach except that her choices are horrible. The author sticks with (pretty much) one example that makes no sense unless you are 13 (I love Facebook as much as everyone else, but I don't see it as a CLEAR example of any of the patterns). Despite others negative reviews (very similar to my own) I purchased the book because I am a big fan of the O'Reilly books. Don't make the same mistake I did.

NONE
09 March, 2010

Should have listened to other reviewers

This is my first ever Amazon review. After buying this book and reading almost the complete thing (1 chapter shy of the end) I am incredibly disappointed. There is barely any explanation as to how and why the individual patterns are used. Instead the author focuses on examples, which could have been a good approach except that her choices are horrible. The author sticks with (pretty much) one example that makes no sense unless you are 13 (I love Facebook as much as everyone else, but I don't see it as a CLEAR example of any of the patterns). Despite others negative reviews (very similar to my own) I purchased the book because I am a big fan of the O'Reilly books. Don't make the same mistake I did.

NONE
09 March, 2010

Should have listened to other reviewers

This is my first ever Amazon review. After buying this book and reading almost the complete thing (1 chapter shy of the end) I am incredibly disappointed. There is barely any explanation as to how and why the individual patterns are used. Instead the author focuses on examples, which could have been a good approach except that her choices are horrible. The author sticks with (pretty much) one example that makes no sense unless you are 13 (I love Facebook as much as everyone else, but I don't see it as a CLEAR example of any of the patterns). Despite others negative reviews (very similar to my own) I purchased the book because I am a big fan of the O'Reilly books. Don't make the same mistake I did.

NONE
09 March, 2010

Should have listened to other reviewers

This is my first ever Amazon review. After buying this book and reading almost the complete thing (1 chapter shy of the end) I am incredibly disappointed. There is barely any explanation as to how and why the individual patterns are used. Instead the author focuses on examples, which could have been a good approach except that her choices are horrible. The author sticks with (pretty much) one example that makes no sense unless you are 13 (I love Facebook as much as everyone else, but I don't see it as a CLEAR example of any of the patterns). Despite others negative reviews (very similar to my own) I purchased the book because I am a big fan of the O'Reilly books. Don't make the same mistake I did.

NONE
09 March, 2010

Should have listened to other reviewers

This is my first ever Amazon review. After buying this book and reading almost the complete thing (1 chapter shy of the end) I am incredibly disappointed. There is barely any explanation as to how and why the individual patterns are used. Instead the author focuses on examples, which could have been a good approach except that her choices are horrible. The author sticks with (pretty much) one example that makes no sense unless you are 13 (I love Facebook as much as everyone else, but I don't see it as a CLEAR example of any of the patterns). Despite others negative reviews (very similar to my own) I purchased the book because I am a big fan of the O'Reilly books. Don't make the same mistake I did.

NONE
09 March, 2010

stick to the concept of introducing a pattern

seems like all pattern books (authors admit) get caught up in the example.

One author (Cooper) got caught up in (his kids I guess) an app handling swimming competition.

Another caught up in fire works manufacture.

I started "fixing" the examples in the "gang of four" book.

Landon M. Kelsey III
02 November, 2009

stick to the concept of introducing a pattern

seems like all pattern books (authors admit) get caught up in the example.

One author (Cooper) got caught up in (his kids I guess) an app handling swimming competition.

Another caught up in fire works manufacture.

I started "fixing" the examples in the "gang of four" book.

Landon M. Kelsey III
02 November, 2009

stick to the concept of introducing a pattern

seems like all pattern books (authors admit) get caught up in the example.

One author (Cooper) got caught up in (his kids I guess) an app handling swimming competition.

Another caught up in fire works manufacture.

I started "fixing" the examples in the "gang of four" book.

Landon M. Kelsey III
02 November, 2009

stick to the concept of introducing a pattern

seems like all pattern books (authors admit) get caught up in the example.

One author (Cooper) got caught up in (his kids I guess) an app handling swimming competition.

Another caught up in fire works manufacture.

I started "fixing" the examples in the "gang of four" book.

Landon M. Kelsey III
02 November, 2009

stick to the concept of introducing a pattern

seems like all pattern books (authors admit) get caught up in the example.

One author (Cooper) got caught up in (his kids I guess) an app handling swimming competition.

Another caught up in fire works manufacture.

I started "fixing" the examples in the "gang of four" book.

Landon M. Kelsey III
02 November, 2009

stick to the concept of introducing a pattern

seems like all pattern books (authors admit) get caught up in the example.

One author (Cooper) got caught up in (his kids I guess) an app handling swimming competition.

Another caught up in fire works manufacture.

I started "fixing" the examples in the "gang of four" book.

Landon M. Kelsey III
02 November, 2009

stick to the concept of introducing a pattern

seems like all pattern books (authors admit) get caught up in the example.

One author (Cooper) got caught up in (his kids I guess) an app handling swimming competition.

Another caught up in fire works manufacture.

I started "fixing" the examples in the "gang of four" book.

Landon M. Kelsey III
02 November, 2009

stick to the concept of introducing a pattern

seems like all pattern books (authors admit) get caught up in the example.

One author (Cooper) got caught up in (his kids I guess) an app handling swimming competition.

Another caught up in fire works manufacture.

I started "fixing" the examples in the "gang of four" book.

Landon M. Kelsey III
02 November, 2009

Not bad, but I wouldn't buy it again

There's definitely some usable information and examples, but most of the examples and discussion smell a little off and contrived, as if Bishop doesn't really understand the topic at hand, and was given a little help with the code snippets (giving the impression of two different voices in the text).

The main reason I purchased this book was that it was available in PDF format (from O'Reilly) and the examples were in C#, making it a promising reference PDF to have on my thumb drive at work sites. While I have gotten some value out of it, I find myself continually skipping over this in favor of a PDF I have of the GoF patterns in UML.

I wouldn't recommend it as an educational or reference text if you are able to take a print edition of a strong text with you. If I had the choice to rethink my purchase, I probably wouldn't buy it.

Honkeywrench
27 September, 2009

Not bad, but I wouldn't buy it again

There's definitely some usable information and examples, but most of the examples and discussion smell a little off and contrived, as if Bishop doesn't really understand the topic at hand, and was given a little help with the code snippets (giving the impression of two different voices in the text).

The main reason I purchased this book was that it was available in PDF format (from O'Reilly) and the examples were in C#, making it a promising reference PDF to have on my thumb drive at work sites. While I have gotten some value out of it, I find myself continually skipping over this in favor of a PDF I have of the GoF patterns in UML.

I wouldn't recommend it as an educational or reference text if you are able to take a print edition of a strong text with you. If I had the choice to rethink my purchase, I probably wouldn't buy it.

Honkeywrench
27 September, 2009

Not bad, but I wouldn't buy it again

There's definitely some usable information and examples, but most of the examples and discussion smell a little off and contrived, as if Bishop doesn't really understand the topic at hand, and was given a little help with the code snippets (giving the impression of two different voices in the text).

The main reason I purchased this book was that it was available in PDF format (from O'Reilly) and the examples were in C#, making it a promising reference PDF to have on my thumb drive at work sites. While I have gotten some value out of it, I find myself continually skipping over this in favor of a PDF I have of the GoF patterns in UML.

I wouldn't recommend it as an educational or reference text if you are able to take a print edition of a strong text with you. If I had the choice to rethink my purchase, I probably wouldn't buy it.

Honkeywrench
27 September, 2009

Not bad, but I wouldn't buy it again

There's definitely some usable information and examples, but most of the examples and discussion smell a little off and contrived, as if Bishop doesn't really understand the topic at hand, and was given a little help with the code snippets (giving the impression of two different voices in the text).

The main reason I purchased this book was that it was available in PDF format (from O'Reilly) and the examples were in C#, making it a promising reference PDF to have on my thumb drive at work sites. While I have gotten some value out of it, I find myself continually skipping over this in favor of a PDF I have of the GoF patterns in UML.

I wouldn't recommend it as an educational or reference text if you are able to take a print edition of a strong text with you. If I had the choice to rethink my purchase, I probably wouldn't buy it.

Honkeywrench
27 September, 2009

Not bad, but I wouldn't buy it again

There's definitely some usable information and examples, but most of the examples and discussion smell a little off and contrived, as if Bishop doesn't really understand the topic at hand, and was given a little help with the code snippets (giving the impression of two different voices in the text).

The main reason I purchased this book was that it was available in PDF format (from O'Reilly) and the examples were in C#, making it a promising reference PDF to have on my thumb drive at work sites. While I have gotten some value out of it, I find myself continually skipping over this in favor of a PDF I have of the GoF patterns in UML.

I wouldn't recommend it as an educational or reference text if you are able to take a print edition of a strong text with you. If I had the choice to rethink my purchase, I probably wouldn't buy it.

Honkeywrench
27 September, 2009

Not bad, but I wouldn't buy it again

There's definitely some usable information and examples, but most of the examples and discussion smell a little off and contrived, as if Bishop doesn't really understand the topic at hand, and was given a little help with the code snippets (giving the impression of two different voices in the text).

The main reason I purchased this book was that it was available in PDF format (from O'Reilly) and the examples were in C#, making it a promising reference PDF to have on my thumb drive at work sites. While I have gotten some value out of it, I find myself continually skipping over this in favor of a PDF I have of the GoF patterns in UML.

I wouldn't recommend it as an educational or reference text if you are able to take a print edition of a strong text with you. If I had the choice to rethink my purchase, I probably wouldn't buy it.

Honkeywrench
27 September, 2009

Not bad, but I wouldn't buy it again

There's definitely some usable information and examples, but most of the examples and discussion smell a little off and contrived, as if Bishop doesn't really understand the topic at hand, and was given a little help with the code snippets (giving the impression of two different voices in the text).

The main reason I purchased this book was that it was available in PDF format (from O'Reilly) and the examples were in C#, making it a promising reference PDF to have on my thumb drive at work sites. While I have gotten some value out of it, I find myself continually skipping over this in favor of a PDF I have of the GoF patterns in UML.

I wouldn't recommend it as an educational or reference text if you are able to take a print edition of a strong text with you. If I had the choice to rethink my purchase, I probably wouldn't buy it.

Honkeywrench
27 September, 2009

Not bad, but I wouldn't buy it again

There's definitely some usable information and examples, but most of the examples and discussion smell a little off and contrived, as if Bishop doesn't really understand the topic at hand, and was given a little help with the code snippets (giving the impression of two different voices in the text).

The main reason I purchased this book was that it was available in PDF format (from O'Reilly) and the examples were in C#, making it a promising reference PDF to have on my thumb drive at work sites. While I have gotten some value out of it, I find myself continually skipping over this in favor of a PDF I have of the GoF patterns in UML.

I wouldn't recommend it as an educational or reference text if you are able to take a print edition of a strong text with you. If I had the choice to rethink my purchase, I probably wouldn't buy it.

Honkeywrench
27 September, 2009

A must read book

I own several books on design patterns. Each one is unique and focus on something different. When I bought this book I was little skeptical because of the size. I took me one year to finish it. It is the best book I own on design patterns by far margin. If you are developer this book is not for you. This book is for an Engineer. The UML diagrams are basically driving everything. On top of that every example works the way it is described showing you how things are done. had fun reading it.

Ivan Assenov
24 September, 2009

A must read book

I own several books on design patterns. Each one is unique and focus on something different. When I bought this book I was little skeptical because of the size. I took me one year to finish it. It is the best book I own on design patterns by far margin. If you are developer this book is not for you. This book is for an Engineer. The UML diagrams are basically driving everything. On top of that every example works the way it is described showing you how things are done. had fun reading it.

Ivan Assenov
24 September, 2009

A must read book

I own several books on design patterns. Each one is unique and focus on something different. When I bought this book I was little skeptical because of the size. I took me one year to finish it. It is the best book I own on design patterns by far margin. If you are developer this book is not for you. This book is for an Engineer. The UML diagrams are basically driving everything. On top of that every example works the way it is described showing you how things are done. had fun reading it.

Ivan Assenov
24 September, 2009

A must read book

I own several books on design patterns. Each one is unique and focus on something different. When I bought this book I was little skeptical because of the size. I took me one year to finish it. It is the best book I own on design patterns by far margin. If you are developer this book is not for you. This book is for an Engineer. The UML diagrams are basically driving everything. On top of that every example works the way it is described showing you how things are done. had fun reading it.

Ivan Assenov
24 September, 2009

A must read book

I own several books on design patterns. Each one is unique and focus on something different. When I bought this book I was little skeptical because of the size. I took me one year to finish it. It is the best book I own on design patterns by far margin. If you are developer this book is not for you. This book is for an Engineer. The UML diagrams are basically driving everything. On top of that every example works the way it is described showing you how things are done. had fun reading it.

Ivan Assenov
24 September, 2009

A must read book

I own several books on design patterns. Each one is unique and focus on something different. When I bought this book I was little skeptical because of the size. I took me one year to finish it. It is the best book I own on design patterns by far margin. If you are developer this book is not for you. This book is for an Engineer. The UML diagrams are basically driving everything. On top of that every example works the way it is described showing you how things are done. had fun reading it.

Ivan Assenov
24 September, 2009

A must read book

I own several books on design patterns. Each one is unique and focus on something different. When I bought this book I was little skeptical because of the size. I took me one year to finish it. It is the best book I own on design patterns by far margin. If you are developer this book is not for you. This book is for an Engineer. The UML diagrams are basically driving everything. On top of that every example works the way it is described showing you how things are done. had fun reading it.

Ivan Assenov
24 September, 2009

A must read book

I own several books on design patterns. Each one is unique and focus on something different. When I bought this book I was little skeptical because of the size. I took me one year to finish it. It is the best book I own on design patterns by far margin. If you are developer this book is not for you. This book is for an Engineer. The UML diagrams are basically driving everything. On top of that every example works the way it is described showing you how things are done. had fun reading it.

Ivan Assenov
24 September, 2009

.NET Developer Group Coban

Este libro es excelente porque puedo encontrar temas de diseno en C#. Tiene muchos ejemplos y de esa manera se hace muy facil aprender a programar adecuadamente el lenguaje. Tambien tiene estructura de patrones y ejemplos especificos qu eme ayudaran al buen manejo de C# 3.0.

By:

Jose Rolando Guay Paz
19 July, 2009

.NET Developer Group Coban

Este libro es excelente porque puedo encontrar temas de diseno en C#. Tiene muchos ejemplos y de esa manera se hace muy facil aprender a programar adecuadamente el lenguaje. Tambien tiene estructura de patrones y ejemplos especificos qu eme ayudaran al buen manejo de C# 3.0.

By:

Jose Rolando Guay Paz
19 July, 2009

.NET Developer Group Coban

Este libro es excelente porque puedo encontrar temas de diseno en C#. Tiene muchos ejemplos y de esa manera se hace muy facil aprender a programar adecuadamente el lenguaje. Tambien tiene estructura de patrones y ejemplos especificos qu eme ayudaran al buen manejo de C# 3.0.

By:

Jose Rolando Guay Paz
19 July, 2009

.NET Developer Group Coban

Este libro es excelente porque puedo encontrar temas de diseno en C#. Tiene muchos ejemplos y de esa manera se hace muy facil aprender a programar adecuadamente el lenguaje. Tambien tiene estructura de patrones y ejemplos especificos qu eme ayudaran al buen manejo de C# 3.0.

By:

Jose Rolando Guay Paz
19 July, 2009

.NET Developer Group Coban

Este libro es excelente porque puedo encontrar temas de diseno en C#. Tiene muchos ejemplos y de esa manera se hace muy facil aprender a programar adecuadamente el lenguaje. Tambien tiene estructura de patrones y ejemplos especificos qu eme ayudaran al buen manejo de C# 3.0.

By:

Jose Rolando Guay Paz
19 July, 2009

.NET Developer Group Coban

Este libro es excelente porque puedo encontrar temas de diseno en C#. Tiene muchos ejemplos y de esa manera se hace muy facil aprender a programar adecuadamente el lenguaje. Tambien tiene estructura de patrones y ejemplos especificos qu eme ayudaran al buen manejo de C# 3.0.

By:

Jose Rolando Guay Paz
19 July, 2009

.NET Developer Group Coban

Este libro es excelente porque puedo encontrar temas de diseno en C#. Tiene muchos ejemplos y de esa manera se hace muy facil aprender a programar adecuadamente el lenguaje. Tambien tiene estructura de patrones y ejemplos especificos qu eme ayudaran al buen manejo de C# 3.0.

By:

Jose Rolando Guay Paz
19 July, 2009