Thanks for the guidance.  In fact it basically works but there is an archtectural glitch.  We derived a class as follows

    partial class PseudoControlPanel : DotNetNuke.UI.ControlPanels.ControlPanelBase

and instantiated it to call AddNewModule() (or AddExistingModule()) but it generates a reference not set error on the Request object.

So we copied the code for these functions out of ControlPanelBase and into our own class where we have a valid request object.  Everything works fine as far as we can tell.  So thank you much for that.  But there is a problem...

We have copied some 100 lines of source out of your release so if that code changes in a new release we may have to rework everything.

Our question is whether the dev team could make the Request object not read only in a coming release, or provide a method to set it, or otherwise make the two very valuable methods AddNewModule() and AddExistingModule() usable from application code.  As far as we can tell this is very easy since the only glitch was the Request object used at the very end.

Thank.s