Quote Originally Posted by Niya View Post
...as far as the .Net is concerned, it's type library is broken.
Well, as long as the true COM-tools have no problem with referencing it (VB6 and VBA as well as TwinBasic and VBScript),
I'm not really interested in, what the .NET-Typelib-parser throws out as warnings.

Quote Originally Posted by Niya View Post
... it even found an interface that is not derived from IUnknown:-
Code:
Warning        Processing COM reference "VB" from path "C:\Program Files (x86)\Microsoft Visual Studio\VB98\VB6.OLB". Type library importer has encountered an interface not derived from IUnknown: '___MSJetSQLHelp'.
This indicates, that the .NET typelib-parser goes "one level too deep" in its "COM-reference-imports" -
(trying to resolve also implemented interfaces, instead of being satisfied with the Default-interface of a Class) -
and besides, I'm not the Author of 'VB6.olb', Microsoft is...

Quote Originally Posted by Niya View Post
This is one of the rare instances where your library actually covers something that isn't by the .Net ecosystem...
Well, SQLite-wise there's a lot more missing, as e.g.:
- Zip-support
- CSV-support
- superfast JSON-serialization of queried Resultsets
- JET-Sql-Function-support as e.g.: Left$, Mid$, Right$, DateDiff, DatePart

Graphics-wise:
- SVG Read/Write support
- Alpha-Channel-JPGs
- ControlPoints-support
- ...plus a lot more convenience-stuff, not found in .NET

At least proper JSON-support was recently included in .NET (though long after the RC-lib shipped with it).

Olaf