This post originated from an RSS feed registered with .NET Buzz by Scott Watermasysk. Original Post: Community Application Blocks Feed Title: ScottW's ASP.NET WebLog Feed URL: /error.aspx?aspxerrorpath=/blog/rss.aspx Feed Description: ASP.NET and Blogging Latest .NET Buzz Posts Latest .NET Buzz Posts by Scott Watermasysk Latest Posts From ScottW's ASP.NET WebLog

Ron Jacobs (who finally made a post :) of the Patterns and Practice group is asking about how application blocks should be further developed and what other blocks you would like to see.

The problem I have is that there are so many good ideas that could be made into application blocks that our team could never get them all done.  The more I thought about this the more I began to wonder if there was some way in which we could turn the community loose on application blocks and let them build their own.

 Alex left a comment suggesting using groups the Regional Directors, MVPs, and ASPInsiders to help continue the development of more blocks.

Get the Regional Directors, MVPs, and other groups like the ASPInsiders (http://aspinsiders.com) involved in the construction of the application blocks. I think with PAG guidance these groups could apply their "finger on the pulse" connection to the development community and produce some great application blocks.

I think Alex's suggestion could lead to something great. Having a central authority oversee the process with set rules, design guidelines, testing standards, etc could result in very useful library of blocks.

When I was working on the .Text search engine code, the only documentation I could find on Lucene.Net, was the the Jakara overview of the java version. I do not have any experiences using java, so the Jakarta site was new to me, but it seems to be filled with some great open source products. Imagine going to to a site, clicking a couple of checkboxes, and then downloading a useful library of tested and trusted code which could knock weeks or months off of your dev cycle.