ursus zeta

Hi eligeti vinod, It's me, ursus zeta, from CodeProject. I googled your Link error code and discovered that you've posted all over the Internet. And I can't seem to get into the CodeProject for some reason,... Anyway, after rereading your C++ command Line and Linker options, I noticed that you used the "/clr" switch, making your DirectShow filter DLL a managed .NET DLL. I don't know if you are aware of it, but, the DirectShow object libriaries are 'unmanaged' COM libraries; .NET and COM types are NOT compatible. I assumed you were aware of this when I responded to your original post. When using COM components in .NET applications, the correct technique is to use System.Runtime.Interop which manages the data exchange between the two entities. The COM Interop creates wrappers for all COM types so that they are usable in a .NET environment. In your case, I think that you want to create an application that is unmanaged (by the Common Language Runtime); in other words, a Win32 application. Review the Samples that accompany the C++ DirectShow SDK, and you will see that they do not use the /clr switch. This is from the DirectShow FAQ at the MSDN site: Will DirectShow ever be accessible through managed code? There are no current plans to implement a "Managed DirectShow" platform. You can use COM interop to create DirectShow client applications in managed code, but creating filters that depend on the Common Language Runtime (CLR) is not recommended for performance reasons.