MDAC SDK Conformance testing & .NET!
Hi there,
I have recently upgraded to .NET 2003 and would like to use the OLE DB conformance testing tools, supplied with MDAC 2.8 to test a writable OLE DB provider. The trouble is I cant build the tools as they make use of ANSI C++ and obsolete header files. The documentation only includes directions for VC5 & 6 users and no information for .NET users. Are there any conformance testing tools that will work with .NET or is it possible to obtain pre-built test modules for LTM?
regards chris
i've managed to build the privlib by converting to standard C++, switching from libci.lib to libcp.lib and completely axing one function that utilises a mysterious header called msxmloledb.h. Though doing so renders it unusable due to unresolved externals.
The msxmloledb.h header file seems to be quite obscure and I cant find any info on it or any of the symbols such as it defines such as DBPROPSET_XML_DBINIT.
My patience with msdn and google on the subject is completely exhaused. Is the MDAC SDK obsolete? i can't believe that a functional OLE DB testing tool is not avaliable with visual studio .NET... am i missing something?
If you know anything about this please help i'll get a right grilling if i dont get it sorted!
Try this :-
(1) Edit cmodinfo.cpp and remove the following lines:
#define MSXMLOEDDBINITCONSTANTS
#include "msxmloledb.h"
(2) Remove the entire function GetInitPropsXMLOLEDB in both cmodfinfo.cpp and cmodinfo.hpp.
(3) In miscfunc.cpp: Remove the “if” statement calling GetInitPropsXMLOLEDB, leaving the call to GetInitProps().
/*
// Setup the arrays needed for init, based on string LTM passed to us
if ( !GetModInfo()->GetInitPropsXMLOLEDB(&cPropSets, &rgPropSets) )
*/
TESTC(GetInitProps(&cPropSets, &rgPropSets));
I think this should work around this specific issue.
SirajLala,
Thanks for the help, removing the define and function call did avoid the unresolved external issue but unfortunatly as soon as a test module is selected within LTM the thing GPF's. I've not spent much time looking into why; I'm wondering if I would be better off forgetting that the conformance tests exist.
Have you successfully used LTM to test a provider? Is it worth persuing?
obviously not.
I cant understand why these tests have not been updated with MDAC 2.8! Microsoft realeased Visual Studio .NET 2003 with ATL support for writable providers then a year after that released MDAC SDK 2.8 but couldnt be bothered to update the conformance tests.
This is making me paranoid that they are actually trying to hinder the development of third party database systems. If this is the case it's very tight because many developers spend out lots of mulla to get development tools that should make our lives easier. Now it looks like we must also develop our own OLE DB conformance testing kit, maybe microsoft could also convert all the doumentation to urdu.
troll out!
