I've been using the Microsoft VC product since v1.0 on Windows 3.1. I'm always appreciative of the QA that goes into the compiler especially. It drifted from the C++ standard several times but they've always brought it back in line (mostly). I've never found any big bugs in the compiler, just the IDE environment (which has a different QA team).
Very cool. But kinda glanced over the API stuff. I see a need to raise the bar for audio for the .Net developer. Say I want to create a ~simple DJ app that has at least two mp3/wma streams. So I need to be able to manage and mix the two streams, have cue points, some kinda event callbacks to update the audio graph with fine detail. Simple way to enum and select ouput devices and input devices, etc. So simple Load() and Play() on a Media player control does not really cut it anymore. Is the API going to be "at least" this rich for us for .Net? Thanks much.
I totally agree with you about the .Net situation. The limited DirectShow wrapper in .Net doesn't give you the flexibility you need as you're aware. Of course this is all available in the real world DirectShow (unmanaged), so the problem is not with low level services but rather with the .Net wrapper. I'm not expecting to see any of this change for the Vista version of .Net, most Audio developers stay in unmanaged space so that they can have the tightest control possible over latency. Note that your example is possible by using the unmanged version of DirectShow via COM Interop, Media Foundation should have something similar.
Chris Parsons [MVP DirectShow/DirectX/Platform SDK]