This project is read-only.

.communities Frequently Asked Questions


Q: So what is .communities?
A: .communities started out as the Community Advanced Starter Kit project (CASK for short) and was intended as a .NET 2.0 version of the Community Starter Kit sample application released by Microsoft for the .NET Framework 1.0. The CASK project was led by BillKrat and is now supported solely for his customers. I joined the CASK project in 2006 and extended the functionality somewhat by adding a new Administration theme, RSS feeds and a number of other small enhancements. Unfortunately, Bill could not continue supporting the CASK as an open-source project as he did not have the time to work on it with his other commitments, so I decided to branch off from his codebase during the refactoring phase of development - changing the name to .communities so that it would not be confused with the CASK project.

Q: How do I join the .communities project?
A: The short answer is that you cannot join the project at the moment. The reason for this is that I am developing .communities as a showcase application to demonstrate my .NET skills to potential customers, so if other developers start adding code to the solution, there will be no way to differentiate between my code and anyone elses.

Q: I would really like to help out with .communities though - how can I do this?
A: If you are interested in contributing then you can still help out by participating in the discussions. If after discussion, I decide that there is a bug in the code, or that there is an idea that will enhance the .communities codebase, then the discussion will be converted to a work item. You can also add a patch to the source code and once it is approved, I will merge it with the existing code citing you as the developer responsible for the update.

Q: When will .communities be released?
A: The initial version will be released when I get time to complete the initial requirements, this version will contain all the core framework code and is intended as a Test Build to "iron out" any bugs that the framework may contain. Once this task is completed, the next set of releases will concentrate on module development culminating in the final release that will contain the Installer and Upgrade Wizards.

Last edited Aug 1, 2007 at 2:24 PM by CSharpEd, version 2


No comments yet.