Probably, the same place as the python bindings. In oisaddons - as, it is not really part of the main lib.
I can setup a module in cvs for you, something like:
oisaddons/DotNet
That is, if you want cvs access to that. I could also just place it there if you don't want to do anything more with it.
I recommend that all addon modules maintain that path setup (for easier source building).
ParentPath
|-oisaddons
| |-python
| |-DotNet
| |-demos
| |-Gesture
|- ois
Basically, if oisaddons is always in the same parent path as ois, setting up relative paths is easy for all projects. Nice to see you have made great progress
