We tried out ScrewTurn and LiteWiki, after investigating a few more but found problems with most. They were ok, but nothing could quite match the reliability, feature set and 3rd party plugins of MediaWiki. As we were already running PHP, MySQL and ISAPI ReWrite, it was no issue for us to run it on our Microsoft Servers.
If you do find something, let me know. If you can get MediaWiki running, you won’t regret it

Dave

Nice post, im currently looking at a wiki to hold all info about our work websites from holding the high level change log, keep track of bugs, holding info about error codes and our customer support using it as an internal help area.
Did you come across any good .net wikis as it would be easier if i can just whack it on an existing server in the building, we too are all Microsoft servers.

Thanks
Stu

I would keep SVN comments for information specific to the file(s) being checked in. Generally if you’re working on a file, it makes sense to check it’s version history first to understand how it got to this point.

The wiki should be for generalised information on a website / project, and information that is useful across multiple projects. A wiki’s real power lies in the links.

Of course it’s up to you how you use it, I’d be interested to know how you get on.

So would you say that the information in the Wiki would be the same or similar information you would put in some kind of source control such as SourceSafe or SVN?

Thanks for the insight.
Jonathan