best Continuous Integration approach

stash + bamboo, for a small team, it only costs $20, host in house,
use confluence ($10) for team collaboration, host in house,
trello(free) to manage daily scrum / project process.
jira? not every useful for a small team

team collaboration on git branch vs folk

sBranch:
one public remote repository, everybody push to the remote repo using different branch, and merge to the developer branch at completion, send pull request to merge to master branch

Folk:
one public remote repo, one private remote repo for every dev. dev checkin to private repo, and merge to private repo when public repo is updated. raise a pull request at completion and push to public repo.

the advantage of folk:
1: keep the public repo clean, only see one clean push for each push, no need to see lots of bug fix, style formatting….
2: isolate dev private repo, if anything went wrong, there is no impact on public repo, they can simply refolk again.
2: when multiple pull request occurred, branch may have to rewind multiple pull request, but folk, only need to roll back the specific push (not quite understand how this works)

Use Service Stack for Web Service

vs WCF: easy to integrate for RESTful service
vs Web Api: automatic featured documentation, wsdl for xml
pro:
not rely on any other service package, keep nuget clean.
authentication
full format support, json, jsonp, xml, csv?…

Map a windows folder to driver

Map C:\abc to D:\ drive (http://en.wikipedia.org/wiki/SUBST#Persisting_across_reboots)

• •  In registry – go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\DOS Devices
  • Add “D:” key with value “\??\C:\TFS”