You seem to mixing & matching tools. The VS.NET 'add web reference' wizard only works with XML web services, not remoting.
Remoting can handle everything you're trying, and the CLR-based serialization that's involved certainly pays attention to your use of the NonSerialized attribute. But the WSDL that's returned for a remoted object is different than the WSDL that's returned for an XML web service. The VS.NET add web reference wizard (and underlying wsdl.exe proxy generator) are simply not designed for use with remoting. Remoting's proxy generated is called soapsuds.exe, and there is no integrated wizard in VS.NET that supports it. You have to build/distributed your own assemblies (for example, assemblies with interfaces or other shared types in them), or use soapsuds.exe from the command line to generate client-side shims in the same manner as wsdl.exe is used for XML web services. -Mike DevelopMentor http://staff.develop.com/woodring > > -----Original Message----- > From: Moderated discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of > Simon Jenkins > Sent: Thursday, July 17, 2003 6:34 AM > To: [EMAIL PROTECTED] > > I am trying to remote and object over http channel using the SOAP > formatter so that I can add a web reference to my remoted object > allowing me to reference it from the compact framework.
