Weather you are a regular Internet user or a sysadmin surf from/work in Cambodia.
I got to tell you this stop rely on your ISP DNS server they are bully blocky slavery sh*@#t now it time to go looking for a more reliable, safer, faster, smarter and best if it is FREE DNS server solution.

Lady & Gen. I introduce to you OpenDNS [ for more information click here and read for yourself ].

It had been quiet a while since I tried to allocate some time to get in deep with Rhino-Tools and my previous attempt was not fruitful. However I had learn that most of the problem that prevent me to run the sample project with the latest build (local build) because there is a mismatch assembly used.

Minimum Assembly Reference

The typical Rhino-Tools sample applications always make reference to assembly files stored in the SharedLibs in each sample applications’ folder and after every successful build of Rhino-Tools I always want to run the sample application again to see if it break anything. What I usually do is to copy assembly file from the ..\Build\net-2.0\debug & ..\SharedLibs\Castle folder to SharedLibs located in individual sample application folder.

This step is such a pain an annoying. I want to setup a system which I could later on forget about it. So to fix the problem one and for all is to reference needed assembly from it original location ..\rhino-tools\SharedLibs\Castle and ..\rhino-tools\build\net-2.0\debug this way we do not waste disk space for storing the same assemly files and since it is a sample project it doesn’t hurt a ship by doing so.

However I still recommend to copy the needed assembly to private folder and reference from there if you are working with your real world application.

Until this solution is adopted I need to add svn ignore roles SharedLibs in each sample applications folder.