title: WCF Webservice with an ASMX interface returning a Stream
body: <p>I have a WCF service for inter-system, inter-network integration.  The service was originally created with just the WCF SVC interface, but because of requirements that came to light after deveopment we needed to add an ASMX interface to the service.</p>
  
  <p>Now, all of this has worked just fine so far.  It's only now that we've added two new methods to the web service, one of which accepts a <code>System.IO.Stream</code> as one of its parameters, and another which returns a <code>System.IO.Stream</code>, that we've encountered a problem.</p>
  
  <p>The WCF interface happily works with these two Streams.  The ASMX interface, when referenced by the client as as Web Reference, appears to have created an abstract class in its auto-generated client code: <code>public abstract class Stream</code>.</p>
  
  <p>Has anyone else tried this before?  I'm trying to figure out what my options are.  Right now I'd like to keep things as they are, if there's just one small component I'm missing.  If not, could I perhaps create two copies of these Stream methods, one that takes a Stream and the other taking a byte array, and add attributes so that WCF exposes one, and ASMX exposes the other?</p>