Hi all,

I'm trying to create COM wrapper around a class that needs to use remoting
to perform its tasks, so that I can unload the AppDomain after it's done.

I've build the code to create the AppDomain and load the MarshalByRef object
into the other domain. All works well when running this code in .NET.

However, if I run the exact same code through COM the Remoting through the
AppDomain fails. Specifically it looks like the Proxy is created but it
cannot be cast to the proper type.

public TypeParser CreateTypeParser()
{
if (!this.CreateAppDomain(null))
 return null;

object  T =  this.LocalAppDomain.CreateInstance( "wwReflection",

                             "Westwind.wwReflection.TypeParser" ).Unwrap();

/// *** Ok both in COM and WinForm - returns MarshalByRef object
// System.Windows.Forms.MessageBox.Show( T.GetType().Name   + "\r\n" +
T.ToString() );

// *** this works in WinForm but not in COM. COM get null
TypeParser Parser = T as Westwind.wwReflection.TypeParser;

if (Parser == null)
{
/// this code always fires with COM
 System.Windows.Forms.MessageBox.Show( "Parser is null" );
 return new TypeParser();
}

// Always get a result in WinFOrm
return Parser;

 return new TypeParser();
}

[ClassInterface(ClassInterfaceType.AutoDual)]
[ProgId("wwReflection.TypeParser")]
public class TypeParser : MarshalByRefObject
{
...
}

Using the TypeParser object directly through COM works fine - it appears
something in the Remoting system is behaving very differently in COM hosting
than in WinForm hosting. Note that there is no error for the call to
CreateInstance() as there would be if the type can't found or instantiated.
If I mistype the type name it fails with an exception.

Any ideas on what's different?

+++ Rick ---