Chaps,
I just got home after another day of suffering in a different office. Brendan, I do like to use svcutil to generate proxies for non-Silverlight projects. I wanted to do the same for SL projects but never found out what "trick" the build process was using to generate the code behind the "Add Service Reference". Thanks for pointing out that slsvcutil <http://msdn.microsoft.com/en-us/library/cc197958(v=vs.95).aspx> exists, and I'll give it a bash on the weekend and hopefully it will replace project references and prevent such suffering as I had this morning. I'm familiar with cross-domain errors and have had them before when I accidentally had the service and the client running in different ways (in IIS or the lightweight sever). I guess in my anger this morning I forgot to check in fiddler what was happening, but I didn't change any networking code and didn't expect to find problems there. Chris, "Maybe your Silverlight project is set as the startup project, hence the issue." - I have done this before by accident and it produces a stinkin' mess of misleading errors. I'm not sure if I did it this morning in my confusion. By randomly restoring files I eventually managed to get the projects working again, but I don't know how because I changed so many things so rapidly. Oh well, at least I'm going again for some reason or other. Greg
_______________________________________________ ozsilverlight mailing list ozsilverlight@ozsilverlight.com http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
