I had a look at your Service description file and loaded it into VS.NET, the file displays as a series of non ASCII characters, and would be unintelligable to VS.NET.
On further examination I noticed that the encoding in the XML Processing Instruction header is utf-16 <?xml version="1.0" encoding="utf-16"?> I changed this to utf-8 <?xml version="1.0" encoding="utf-8"?> and the xml displays correctly in VS.NET. I suspect VS.NET does not handle utf-16 encoded XML. Is there any reason why visual studio can't add a web-reference to a mono hosted webservice? Visual Studio 2003 always finds the service; allows one to add it to one's visual studio solution and then removes it again with a "failed to create xml-document". I've tried this scenario on several windows boxes and it is always the same. The microsoft wsdl.exe is perfectly able to generate the code stub, that allows one use the service. The problem seems to lie in the visual studio integration. The service I've written and which shows the above symptoms can be reached here: http://www.fafner-net.dk/aspnet/service.asmx /Morten Krog _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
