Developer Guidelines

Summary

The FlexWiki administrative staff have developed some guidelines to help ensure that FlexWiki continues to evolve as robust and reliable software

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.
Name C# files after the type they contain.
Make sure you're subscribed to the FlexWikiDevelopersList
Make sure you have a WikiHomePage
Make sure you've read the DeveloperHome page for important information about how we do things
Before you commit, make absolutely sure that you aren't breaking anything

If you are fixing a BugReport or fulfilling a FeatureRequest, update the tracker on the SourceForgeProject site.
You must place the LicenseStatementTemplate at the top of every source file.
Every project should contain a link to the SharedAssemblyInfo file (follow the link to learn more)