I'm making a COM interface, ITest
which is part of a test suite running only in a local process. The particular functionality I'm testing is not important but the main point is I will not be using CoCreateInstance()
or any factory objects to instantiate the backing object and get a pointer to the interface. I will simply call a trivial function that looks like this:
HRESULT InstantiateTestObject(ITest ** pptest);
Obviously, I only need a fairly minimal subset of the whole functionality provided by COM.
With that in mind, here's my question.
I understand you can use nul
as a way of telling midl
not to generate a particular file (e.g.midl itest.idl /iid nul
to suppress generating the IID file). If I only plan to instantiate the object backing my ITest
interface via the trivial function shown above, and I only plan to use it in the local process, what is the smallest subset of midl
output files I actually need?