Why I wrote #USBLib and why I don't work on #Develop instead? The answer is as simple as obvious: Chamaeleons. I'm getting two Furcifer Pardalis (Pantherchamaeleons) and I want to give them summer/winter cycles. Therefore I needed a control unit ... in my case an old PC does this job. I used the SIS-PM from Gembird (http://www.gembird.com/) a programmable USB power switch (In germany you can get it from pearl). If you're more interrested in chamaelons (but you need to speak german :)) you can visit my page at ambanja.homelinux.org. There you can download the control software too.

#Assembly has a problem when loading unmanaged .NET DLLs - this affects the DirectX 9 code completion for example. #Assembly will be removed when we do the #D 2.0 port, thus you will have to live with missing code completion for unmanaged .NET DLLs for the 1.x branch. The .NET Reflection API in .NET 2.0 in contrast has everything I can dream of, which is why there will be no further work on #Assembly.

Currently I'm working with Andrea on NRefactory (name may change) which is a merge of #Refactory and VBRefactory. No longer do we need to maintain two different abstract syntax trees or different parser related code. In the past maintenance was an error prone process because each bugfix or enhancement needed to be ported to the other parser layer. Now we're merging VB and C# parsing and have only one representation for the source code. That will prevent many bugs. NRefactory will have a good unit test suite which will ensure that we're not going to break much during code refactoring and future maintenance.