When the string is marshalled as LPSTR it doesn't work the expected way in the client. But it works when it is marshalled as BSTR.
I faced this problem sometime back and put the resolution here http://dotnetjunkies.com/WebLog/swami/archive/2005/08/18/132005.aspx Hope this helps. Thanks, Swami -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of G G Sent: Friday, October 21, 2005 10:17 AM To: [email protected] Subject: Re: [ADVANCED-DOTNET] marshalas attribute ArraySubType Thank you very much. I did find out later that I missed the colon. Despite the fix and the successful build, I am still struggling to make the .net com class to pass string array or any array back to the COM client. The COM client is not .net and is the legacy type application. However the COM client is fully compliant with OLE, OCX. May even be COM+ compliant but I am not positive. I must have missed out on something on the COM binary standard. I guess I have to research some more unless someone happened to have experience with it and could let me know. =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
