The 0.6.0 release added better support for configuring timeouts on the connection to Virtuoso but it turns out that this doesn't solve the original problem that motivated this change because Virtuoso defaults to 30 seconds timeout on its command objects by default. This quite frankly seems dumb to me but then the Virtuoso guys have been decidely sloppy in their writing of .Net code in the past so it isn't entirely suprising. I fail to understand why you ship a database whose default timeout is no timeout but a client that has a default timeout hard coded into it.
Therefore if the user sets a timeout this should be propogated to all VirtuosoCommand objects we use.