ASP.NET 2.0 Providers, source code released

http://weblogs.asp.net/scottgu/archive/2006/04/13/442772.aspx

Check out the details from Scott’s blog. This should be useful for someone who wants to extend ASP.NET using the provider model.

Notes on frequently used patterns

http://codebetter.com/blogs/jeremy.miller/archive/2006/04/11/142665.aspx

Talking about Visitor Design Pattern

 Prakash has blogged a set of links on visitor.

Quote

Visitor Design Pattern

My team had to develop a component using Visitor pattern. Since i have not gone thru this pattern for quite some time, i searched in GOOGLE and found some interesting links.

 

Visitor Defintion:
The visitor pattern allows you to define new, polymorphic operations on a class structure, without touching the source code for the classes themselves. Visitor lets you define a new operation without changing the classes of the elements on which it operates.

 

Useful Links on Visitor Pattern

http://spaces.msn.com/sendhil/Blog/cns!1pEAvDKHzqdnoBanjVFcE_Mg!330.entry

http://jdj.sys-con.com/read/140105_1.htm
http://www.cs.rice.edu/~cork/book/node62.html
http://www.codeproject.com/csharp/csdespat_6.asp
http://www.butunclebob.com/ArticleS.UncleBob.IuseVisitor
http://www.research.ibm.com/designpatterns/pubs/trouble.html
http://www.c-sharpcorner.com/Code/2003/Feb/PossibleUsage.asp

http://blogs.vbcity.com/jspano/articles/199.aspx
http://www.dotnetdevs.com/articles/ReflectionVisitor.aspx
http://www.devx.com/dotnet/Article/27738
http://rileywhite.com/software/visitorpattern.html

 

 

 

 

What is a good design

http://www.jamesshore.com/Articles/Quality-With-a-Name.html

In essence

Great designs:

• Are easily modified by the people who most frequently work within them,
• Easily support unexpected changes,
• Are easy to modify and maintain,
• and Prove their value by becoming steadily easier to modify over years of changes and upgrades.

The Source Code is the (Final) Design – Get your hands dirty. Follow your design down to the code.

Don’t Repeat Yourself.

Be Cohesive.

Decouple.

Clarify, Simplify, and Refine.

Fail Fast – TDD

Optimize from Measurements

A space to watch – NDepend

A space to watch – NDepend

SOA Q & As

Some SOA Q&As

http://carlaugustsimon.blogspot.com/2006/04/some-qa-on-soa.html

70-529 – Late march

http://www.microsoft.com/learning/exams/70-529.asp I guess this should be live. Should give a go at it i thought.

Let us see 😉

 

TDD Discussions

Jeremy summarizes the TDD discussions going on. Interesting read

http://codebetter.com/blogs/jeremy.miller/archive/2006/03/31/142091.aspx

 

My 2 cents

 

TDD is not a replacement for QA Testing. The earlier you find a bug the cheaper it is to fix it. This is probably a known fact. TDD is trying to identify issues when the codebase is with the developer (earlier in the cycle).

 

TDD is not a replacement for design. CRC cards are at a level of abstraction higher than the deisgn thoughts introduced by TDD.

 

TDD umbrella can include the Automated acceptance tests too. Rather than being a purist and stick to Unit Testing i like the concept of Programmer Tests and Customer tests used by the TDD in Microsoft .NET book (James and Alex). It is more pragmatic.