You can do that. Direct2d will render to a D3D surface so you can use the D3DImage to composite the results into a WPF interface. There are also managed wrappers for Direct2d in the Windows API Codepack that was announced a while ago.
I haven't tried it, but my understanding is that D3DImage is based on D3D 9, while Direct2D is based on D3D 10.1, so while it's perhaps possible, I'm not sure it's straightforward. I'd like to see a code sample before digging in. Also, the Windows API Codepack is only Vista / Win7, not XP, so I'd have to use something other than D2D on XP.
I'm still reading this thread so feel free to comment on the video, the beta, the history series, or pretty much anything else you'd like me to see. I'll do my best to make sure the right people get the message too.
I can't underscore how valuable the previous feedback was in ensuring that the right problems got focus. There's nothing like saying "look I got about 100 niners telling me what a POS the addref dialog is so we can dispense with the 'is this really a problem' part of the conversation"
Even if I already know about the problems your comments are ammunition for me so please give me the straight stuff.
Rico, you have always been a champion of our customers. Thank you!
Niners, please speak up!
C
Well, now that you mention it. It would be good if plugins were never allowed to block any UI. It appears that sometimes in VS2008 you click the "Tools" menu, or right-click a project, or something it takes many seconds (~2-10) to open. I suspect it's one of our plugins misbehaving for some reason, but it would be better if VS basically loaded any plugin UI asynchronously. So maybe that Incredibuild menu item isn't there initially if it's not fast enough (say, 50ms), that's better than its slowness getting in my way the 99% of the times when I'm not actually going for that menu item.
DataSet viewer is not working when used in an application targeted at .Net 3.5. Not that it's that bothersome, but Rico promised excellent side-by-side functionality . The error says something about the visualizer not loaded due to different runtime.
OK, Rico, here's a question for you:
Who's brilliant idea was it to remove support for raster fonts from the VS 2010 editor? They've been supported from the very beginning of Visual C++. How can you compare a font like Consolas or Courier New to a raster font like Terminal for visibility, legibility, and maximum lines per screen, especially at small font sizes (e.g., 9 points and 6 points)? Try comparing these fonts in VS 2008 and tell me your opinion.
Just curious,
Michael Goldshteyn