>>>I've been messing around with some code that uses Shell32.DLL for file browsing that I managed to hack together in C#. I'm looking at doing a rewrite and I was wondering... Is there a compelling reason to stick with C# on this. It seems like it would be a ton easier to write this type of code in C++ and either go mixed mode or pure /CLR with it in C++.
>>>
>>>My C++ is a bit rusty, but it usually comes back pretty quickly. Do C++ CLR DLLs play nicely with C# projects? Any compelling reason to stick with C# for this?
>>
>>So... from the lack of response I'm guessing no c++ programers in the crowd?
>>
>>Well to answer my own question... so far it looks very doable. I can call the shell functions directly from managed c++ code, I can call the c++ dll from c# exactly as if it were a C# dll.
>>
>>My biggest problem is what seems like a complet lack of resources when it comes to c++ managed code. Most of the CLR samples do not show c++ samples and simple things like converting a c++ string to a clr string are hard to find.
>>
>>And I'm running into some small anoiances like my c++ ObservableCollection returning Error 7 not supported by the language in C#. I can work around that if I need to. It's also looking like properties are not correctly supported. I haven't tested that yet.
>
>Since I'm talking to myself... <g>
>
>I might as well finish the conversation...
>
>It's all looking do able. The ObservableCollection just needed an additional pointer reference and I just tested properties and they are working. For me, this seems straight forward compared to pinvoke. So I think I'll continue with it.

You weren't talking to yourself. I was listening with interest but had nothing constructive to say :-}