|Type: Feasibility Demonstration||Project ID: P050302|
|Style: Abbreviated||Status: In Progress|
|Assigned To: Dennis E. Hamilton||Defined By: Dennis Hamilton (2004-11-11)|
|Date Initiated: 2005-03-07||Date Completed: tbd|
2005-03-07: Extract the necessary skeleton
and any local headers from the Sample DMS to the
moved to separate DeRisk01 project.]
The result is a simple file (or two) that will compile to a simple stub, provided that the necessary definition files are available.
Arrange for the function to simply return NOINTERFACE, along with a NULL interface-pointer value.
Get the DLL to compile.
Use DeRun01 to verify that the DLL can be called and it behaves properly, just as other DMS DLLs called by DeRun01.
Create registration and deregistration scripts to register the dummy as the default DMS, then deregister it.
Attempt to operate the DMS with TestODMA32 and also Microsoft Word 2003.
Record enough to be able to fully document this part and the preparations later.
Find out how to learn the location of the DLL that is being run (we need this for other reasons later on)
Use that as the location for creating a log (we will later put the logs in the directory of the document base being used, but for now we put them with the DLL).
Implement a simple log, similar to that produced by the ODMA 2.0 Connection Manager.
Verify operation of the log and the entry failures with TestODMA32 and any Microsoft Office applications that are proposed to be ODMA-aware.
ODMA Interoperability Exchange.
created 2005-03-07-10:04 -0800 (pst) by