Hi Frans,

Here is a suggestions: do decorate your (and perhaps also generated classes by modifying default templates) with DebuggerDisplay attribute. Having core information in a tooltip is even better than debugger visualizers when the info is simple.

Ah, I didn't consider that one that much as I found the debugger figure out some of the info already in the right form and also the debugger visualizers did a good job.

Also, with these things it's often a struggle what to display. PK info might be a good candidate, however in other classes it's not that simple. You have some ideas about which info you might want to see with which types?

Yes, PK is a good candidate for entities indeed - you can quickly figure out which entity you are looking at (well, unless PK is a GUID ). You might also show whether the entity is dirty. For EntityCollection I would show the number of entries and perhaps number of dirty entries (and similar with Context). Then there are predicate expressions (showing something similar to visualizer output without parameters or perhaps with parameter values instead of parameter names). Stuff like that. I have to work a bit more with llblgen to see what exactly would come handy.

Good points. Anyone else who has some ideas about this?

Otis wrote:

Good points. Anyone else who has some ideas about this?

Are attrbiutes inherited? Seems like this should be left up to the developer.

BOb

They can indeed be applied to a partial class. For the entities at least. For the predicate expressions etc. it's difficult, but I think the debug visualizers are more interesting for this.