Continuous Integration Tool--TeamCity

TeamCity is another famous Continuous Integrating Tool. It is much easier to configure than CC.Net because TeamCity is allowed to configure through Web UI. The latter one has too many xml files to configure.

Product Site http://www.jetbrains.com/teamcity/
Free Version License Including

• 3 Build Agents at no additional cost
• 20 User Accounts
• 20 Build Configurations

More detail Info, View the following blogs,

1. Our Build Config--TeamCity(http://blog.eleutian.com/2008/03/07/OurBuildConfigurations.aspx)
2. CruiseControl.NET is dead. Long live Team City!(http://blog.eleutian.com/2007/12/22/CruiseControlNETIsDeadLongLiveTeamCity.aspx)
3. Integration of NCover into Team City for Tech Head Brothers(http://weblogs.asp.net/lkempe/archive/2008/03/30/integration-of-ncover-into-team-city-for-tech-head-brothers.aspx)
4. Continuous Integration Revisited(http://www.zorched.net/2006/08/10/continuous-integration-revisited/)
   

NDbUnit Framework

NDbUnit test is a good UnitTest framework if you are familiar with C#. But this project seems not active since 2006.
Home Page: http://qualitylabs.org/projects/ndbunit/

Safari account

Online Login

Getting started is easy. Just log on to the URL shown below:

URL: http://liqwidkrystal.safaribooksonline.com/?uicode=cognizant

Username: FirstName.LastName@Company.com

Password: 8901704050

How to increase scalability--InfoQ article

http://www.infoq.com/articles/scalability-panel

One Ph.D C# Developer Resume

One good sample resume
http://www.eggheadcafe.com/articles/pbrombergresume.asp

version control with TortoiseSVN without SVN Server

If you only have a limited number of users, and do not need remote access, you can use Tortoise without a subversion server. This makes set-up much easier.
Steps:
1. Install TortoiseSVN software
2. Open Windows Explorer.
3. Create a empty folder as your repository, this can be local or on network drive.
4. Right click the empty folder, and then click on "Create repository here".
5. Then you can use TortoiseSVN--Repository browser to manage your repository directory. Maybe you can add such directories.
-project_a
-trunk
-branches
-tags
6. After the first 5 steps. you can do any operations just like the repository on a SVN Server.

How to arrange the svn repository layout

怎样组织ｓｖｎ的目录其实非常有学问，比如我们是要将多个项目放在一个ｓｖｎ　ｒｅｐｏｓｉｔｏｒｙ下，　还是为每个项目都建立一个独立的ｓｖｎ　ｒｅｐｏｓｉｔｏｒｙ呢？　实际上，　这两种做法各有优缺点．　

使用单一ｓｖｎ　ｒｅｐｏｓｉｔｏｒｙ的优点是：只需要维护一个ｓｖｎ库，工作量自然会少了很多，　这里维护工作包括ｒｏｕｔｉｎｅｌｙ　ｂａｃｋｕｐ，ｄｕｍｐ以及升级ｓｖｎ软件．　当然缺点也很明显：　一个项目的开发人员可以访问另一个项目的文件，另外一个严重的缺点是，每个项目的ｃｏｍｍｉｔ　ｅｍａｉｌ　ｌｉｓｔ很可能不同，　但如果在一个ｒｅｐｏｓｉｔｏｒｙ下，就不能为不同的项目配置不同的ｅｍａｉｌ　ｌｉｓｔ，　这样一旦项目Ａ被ｃｏｍｍｉｔ，项目Ｂ的也会收到ｃｏｍｍｉｔ　ｅｍａｉｌ．　

下面是一个多项目的repository结构，　但项目的ｒｅｐｏｓｉｔｏｒｙ也可参照这个．

要说明的是ｔｒｕｎｋ，ｂｒａｎｃｈｅｓ和ｔａｇｓ的意义，　ｔｒｕｎｋ里面维护着是项目的主要开发版本．　ｂｒａｎｃｈｅｓ是ｔｒｕｎｋ版本的各类分支版本．ｔａｇｓ是保存着ｔｒｕｎｋ和ｂｒａｎｃｈｅｓ的某一时刻的快照．　

/
 calc/
    trunk/
    tags/
    branches/
 calendar/
    trunk/
    tags/
    branches/
 spreadsheet/
    trunk/
    tags/
    branches/