Two Problems in daily building

After downloading the newest Daily Build version of NAnt and modifying the Build file, the problem "NAnt's cvs-checkout task cannot be executed" is finally solved, I suspect this is a Bug of NAnt, but I don't know it seems that few people have encountered this problem (find a user with the same problems as me in NAnt mail archive, but he does not seem to find a solution ).

Now we are going to use CruiseControl. Net to build a continuous building environment. Before that, there are still several problems to solve for NAnt's automatic building.

1. How do I add a Build number during automatic building?
If you do not set the Build number to automatically increase, the daily Build result cannot be seen which Build is completed. When detecting a problem, it cannot correspond to the Build process;
In addition, some Log file names and CVS labels generated during each build need to be automatically generated according to the date and so on. Do you know whether NAnt has a task dedicated to such work?

2. Do you need to unify the settings of the development environment?
When compiling the build file, it is found that the absolute path must be specified for some tools used during the compilation process. In addition, the reference in the DotNet solution also seems to use the absolute path, this is troublesome. in the development process, the working environments of various developers are not completely uniform, and the installation paths of tools are also different. After the code is submitted to CVS, there will certainly be problems when checkout comes out for compilation.
If you specify the path of the Installation tool in the code specification and store the code in a uniform way, this problem will not occur, but this method seems too rigid, I think there should be a better solution.