Clive,

Those errors are a bit more descriptive and are normally what I'd expect. You probably did something special with your original DD so that it was almost correct but was wrong in such a way that it slipped through and got a less useful message (hence the trouble maker moniker).

There seems to be a of confusion about the DD-List. It has nothing to do with Studio DD class modeling and it is not required for view DDO modeling. It is just a list that makes it easier to select and build DD classes and DD objects. DD class modeling works the same way as visual view modeling. The Studio looks at the source and tries to figure out if it can be modeled. Everyone figured this out with view modeling because we don't require any kind of a list to register views. Because we do have a list to register DD classes everyone assumes that this is somehow required for modeling. So people start messing with the DD-List which usually only makes things worse.

If you are having troubles with a DD class, always start by loading it and seeing if it can be modeled. If it cannot, that must be fixed first. You just mess around with the code and keep pressing F7 to see the modeled results. If it cannot model it should provide hints about the problem. When it models, you move forward. Ideally your DD class will be autonomous (ideally all files are autonomous). If they are not and you can't change this, you need to make sure you've got a current project that provides the missing dependencies.

-John