All contributed code must have a corresponding NUnit unit test. Code without sufficient test coverage will not be accepted.
Contributed code should follow the Microsoft Design Guidelines for Class Library Developers.asp. We're not going to be Draconian about it, but adopting a consistent style helps maintainability. Additionally, we may add FxCop enforcement to the build in the future, and following the guidelines goes a long way towards making FxCop happy.
One class/interface/enum per file, please: combining them makes it hard to find things.
The software running this site. -> jump to HomePage
10/22/2006 7:52:17 AM - -81.182.199.248
The software running this site. -> jump to HomePage
10/22/2006 7:52:17 AM - -81.182.199.248
Click to read this topic
6/30/2008 6:40:11 AM - 203.177.74.139
Click to read this topic
9/28/2004 2:31:56 PM - CraigAndera-206.67.217.15
Click to read this topic
9/28/2004 2:31:56 PM - CraigAndera-206.67.217.15
This is the mailing list for people who are developing FlexWiki. Discussion here will likely be technical and focused on the internals of FlexWiki. The general list for users of FlexWiki is the FlexWikiUsersList.
1/24/2008 8:00:59 AM - FLWCOM-jwdavidson
Click to read this topic
11/29/2006 9:31:33 PM - author unknown
Click to read this topic
6/30/2008 6:39:27 AM - 210.212.95.115
An overview of the different kinds of automated tests available for FlexWiki development.