concept Binsor in category .net

This is an excerpt from Manning's book DSLs in Boo: Domain-Specific Languages in .NET.
As mentioned earlier, Rake is a build tool that uses a Ruby-based DSL to specify actions to be taken during the build process (http://rake.rubyforge.org/). Binsor is a DSL for defining dependencies for the Windsor IoC container (http://www.ayende.com/Blog/category/451.aspx). Rhino ETL is a DSL-based extract-transform-load (ETL) tool (http://www.ayende.com/Blog/category/545.aspx). And Watir is an automation DSL for driving Internet Explorer, mostly used for integration testing (http://en.wikipedia.org/wiki/Watir).
Binsor has been around since September 2006. It’s a configuration DSL for the popular IoC Castle Windsor container. In fact, it started life somewhere around March 2006, but it took a while for the idea to come to fruition. Binsor has been actively developed ever since, and has had several major releases since its inception.
One of the major differences between Brail and Binsor is that Binsor scripts tend to be far fewer in number than Brail templates. Where a typical application can have a minimum of a few dozen Brail templates (and I have seen applications with hundreds and thousands), most applications where Binsor is used have only a small number of Binsor scripts, typically one or two. As such, the effect of a breaking change is much less severe. It’s feasible to modify the scripts if necessary.
The versioning approach for Binsor is much more lax than the one used for Brail, but that isn’t to say that breaking changes are acceptable. Breaking changes are still a hassle to deal with, and they should be avoided. But given a good enough reason, breaking changes do and will occur. They tend to be small and focused to limit their effects, but they exist.