[weedweaver]

Has anyone come accross this before, I have a webservice which has a webethod which returns an XMLDocument
e.g.

[WebMethod]
public XmlDocument Test()
{
   //code
	return xmlDoc;
}

I have another project in which i reference the webservice, when this webservice is added the auto generated Reference.cs file is wrong, the method signature is wrong, it thinks the return value is an XMLNode not an XMldocument. i.e.

		public System.Xml.XmlNode Test() {
		   ///bla bla bla
			return ((System.Xml.XmlNode)(results[0]));
		}

I have to manually go into the Reference.cs file and manually change it to XMLDocument!!

Any ideas?? (im using vs2003 by the way)

Thanks

[weedweaver]

Anyone??? Can anyone try this to see if the same thing happens to them??

[PsychoCoder]

I personally have yet to see this happen, and I've written many a Web Service in .Net. I did write a tutorial on the Introduction to web services in C# that may help answer some of your questions, but as far as your particular issue Ive never seen/heard of that happening in a Web Service before.

[weedweaver]

Might be worth creating a simple webservice (if you have time obviously) to see if this happens for you. I have never seen it happen before either, it only seems to be with the XmlDocument datatype.

Thanks

[weedweaver]

Its happened again so it looks a bug in vs2003 to me. Created a simple webservice which returned an XmlDocument (and took one in as a parameter), added this as a reference in a new windows app and the Reference.cs file contained XmlNode not XmlDocument!!! Thats pooop!

[Jayman]

What is the version number of your VS?

You can find this by going to Help -> About Microsoft Visual Studio.

I cannot test it for you because I have long since moved on to VS2005. I would suggest you do the same, if you can.

[weedweaver]

Its not a massive problem, just means i have to manually edit the reference.cs file which is just a bit guff. unfortunately the product is written in .net 2003 so i have to use that for the time being, we do use 2005 and 2008 in other apps however (which is about 50x better)!