This is absolutely ridiculous. I have spent hours on trying to get this thing to work and have had no success. I host a WCF service that is Silverlight enabled on my local machine and it works fine. As soon as I get it to my DiscountASP.Net site, I get error after error. Cross-domain issues, I've deployed a new crossdomain and clientaccess xml files. Handlers issues, I've fixed them. I finally, after two hours straight of tracking every single problem I could got the service file to show up on my site. I've got the most basic of services. I have a valid clientaccesspolicy.xml and crossdomain.xml file on the site in the root directory and still, I get that there are cross-domain issues. This is insane. I can't bill my client for this time because all I've done is run around debugging stuff that shouldn't be an issue in the first place. This is straight-forward. I was just trying to do a proof of concept since I have a much more extensive web service that is waiting for me to put it up on the server, as it failed miserably the last three times I've tried to post it. What is it about hosting a WCF, Silverlight enabled service that is so hard for DiscountASP.Net? I'm about an hour or so away from taking my business elsewhere and all my clients with me.
Well.. WCF / Silverlight is complex.. I have seen many of our customers using WCF w/ Silverlight. I don't think anyone can help if you do not provide any details.
