The old ObjectMapper 2000 was and still is a great tool and I have used it in lots of projects to generate and map my entities.
But one thing that is clear, is that it was way way too complex for most users, it had more settings than the space shuttle and could be a real PITA in some cases.
So me and Mats have talked about adding mapping support inside VS.NET, much like the Linq to SQL mapping designer.
We haven’t actually decided exactly how it’s going to work yet, so there is not much to get excited about for now.
Anyway, I’ve started to build a visual class designer for it.
The control will be possible to use for any kind of Windows Forms project and will not be bound to Object Mapper.
Screenshots:
Main view and overview overlay:
Zoom in and out:
Expand / Collapse:
Custom styles:
I’ve also added some auto layout code to it, but it’s based on spring algorithm, which isn’t very good for class diagrams.
Well, if anyone is interested in some colaboration on this one let me know.
I figure that a decent UML’ish designer could be useful for more than us.
The plan is to release the designer as a standalone project anyway.
Roger Johansson Blog 
Hi Roger,
As I posted in NPersist blog, I am too working on an UML diagram designer replacement for ObjectMapper…
Of course, seeing you doing it on your side made me feel like I just had to throw my work away, but given that :
1) My editor is different enough from yours,
2) The user could be given the choice,
3) We could mutualize our work
4) I finally decided I will continue it anyway as it helps me a lot in learning WPF
I was wondering if the diagram designer could some sort of a plugin,
and I would just need some interfaces…
Best regards,
Jeremy