c# WebService: Why diff on Win vs WP8?

[James Rose]

Ok...  color me frustrated.  I have a WebService and it works fine in my WinForms testbed.  I need to create a Windows Phone 8 app and call this WebService.  I add it but the first thing I notice is that in Solution Explorer the WinForms app shows it under a folder marked "Web Services" (seems right) and this folder is right under the "Service References" folder.  However, within the WP8 app when I add the reference it stays under the "Service References" folder.  Ok, so this might not be a big deal, just an annoyance.  (Hey MS, make sure these things match up if you want us to cross develop)

 

The next point is that in the WinForms app the code is as follows:

FeelzMeServices.FeelzMeSrvc objFMS = new FeelzMeServices.FeelzMeSrvc();
XmlNode xmlReturnNode = objFMS.SaveFeelz(xmlFeelz);

In the Wp8 it is:

FeelzMeService.FeelzMeSrvcSoapClient objFeelzMeService = new FeelzMeService.FeelzMeSrvcSoapClient();
XElement objElement = XElement.Parse(xmlFeelzMe.ToString());
objFeelzMeService.SaveFeelzAsync(objElement);

This code runs, but it never hits the SaveFeelz function within the WebService.  I am running the service locally and can hit it fine in the WinForms, so I know it runs and saves the data...  so wth?  I'd pull my hair out... if I had any.   Any ideas?

[James Rose]

One issue was that I was sometimes testing this locally, and the Emulator needs a collection of settings tweaked...  So I moved on from that and only ran it on my server.

 

The other issue was sending the data via XML.  While I had read several posts that this might not be the best method I moved forward because of other requirements.  I made another function that took in base data types and that worked fine.  

 

This is another one of those moments where I want to bitch slap some developers over at MS for making the same tools work differently on different platforms. (eg Desktop vs Phone)  MS, if you want us to do cross platform, don't do this.

 

Consider this question closed.

[georgevella]

Why are you using xml in the first place?  Have a class and decorate it with the [serializable] attribute.  The piping within .NET will take care of streaming the instance as XML.