TiddlyWikis and a web server

There are a number of options around for making tiddlywikis editable across the web. However, what if all you want to do is to be able to edit locally and have it viewed publicly? If you want to develop on a laptop and make notes along the way, then you would need to edit the file and copy it to the web server across the network. Remembering to do that is just too much work.
Even if you were happy to edit the file directly on the web server across the network, there is a problem in that the tiddlywiki will fail on save if you are accessing it from a network drive.

I tried synchronizing folders with the web server but ran into the problem of saving the wiki, it must have something to do with the naming of the synchronization directory.

But there is a really simple answer, and it integrates into something you are probably already doing. Robocopy! I already have scheduled robocopy scripts that are backing up files to an external drive on the network. Well then, just increase the script to take your wikis to your web server ... done!

The great thing about this approach is that your blog can link to your wikis. Wikis can be more domain oriented, and within the wiki you have your tags for crosslinking.

Who are you impersonating?

Been going through the pains of installing VS Team Foundation Server.
Here are a couple of pointers for others who may be suffering through the same process.
Make sure that Sharepoint, Reporting Services and TFS are all using the same account. That is, LOCAL SERVICE or NETWORK SERVICE but not a combination of BOTH.
Have the user that is creating a process also be a content manager and a administrator within Reporting Services.