Bear in mind, too, that Rotor/Linux implementations are *just* coming out, so it may require a bit of time to settle those out, too.
Rotor does include .NET remoting, both SOAP and binary formatted, but definitely does not include ASP.NET. Ted Neward Architect, UCDavis Account & Financial Services http://www.javageeks.com http://www.clrgeeks.com -----Original Message----- From: Steve Loughran [mailto:[EMAIL PROTECTED]] Sent: Sunday, June 30, 2002 00:14 To: [EMAIL PROTECTED] Subject: Re: now that I've written my doc/lit service... (.NET question) ----- Original Message ----- From: "Miguel A Paraz" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, June 29, 2002 20:41 Subject: Re: now that I've written my doc/lit service... (.NET question) > On Fri, Jun 28, 2002 at 03:54:01PM -0500, Andrew Vardeman wrote: > > Sorry it's kind of off-topic, but call it "interoperability questions" > > If I may add a .NET-development related question: > > Do the .NET web services stuff run on Rotor, Linux or FreeBSD? > Does anyone here have experience with those? > > If they do, I think it would be a good reason to get Rotor set up for > testing web services interoperability, granted that there will be a lot of > .NET nodes out there! > I think .NET remoting does, and that is one of the two .NET SOAP implementations, but as ASP.NET aint in rotor, the other implementation, the .asmx one, is out.
