QUOTE(foosion @ Feb 24 2005, 01:14 PM)
I think you are seriously underestimating the complexity of this. When I said that writing a foobar2000 component ih .NET was theoretically possible, I meant that it is possible for a skilled and very dedicated person.
lol well thanks

I have pulled this off, and it is indeed a fairly complex solution. It was more like a week off and on to get the system working right. Not just days. However, I don't even think I did it "right." It's certainly not "generic." However it does work, and it's really quite amazing.
The main problem is that when using a .NET Form, it wants its own message loop. AFAIK, the only way I could pull this off was using a seperate thread for the .NET Form. This meant communication between threads, which is pretty nasty. Now, I'm a little unsure if it would be possible to hook onto Foobar's message loop using the modeless dialog manager. I don't know how that service works, and using a seperate thread is working okay for me. Perhaps someone could offer suggestions here.
As far as mixing managed and unmanaged code, not really *that* big of a deal when using Managed C++. I wrote everything, including the .NET Form, in Managed C++. I realize that's a pretty perverse thing to do, but it made mixing managed & unmanged just that much easier.
Anyways, JEN, I sent you a PM. I can try to offer any help for people who want to write a .NET plugin... but it is a very complex issue.