Today I ran into unusual problem. Today I want to transfer our Beta 0.7 version to testing server which we just recently bought. As it's works perfectly in my developer machine (does this sounds familiar :p), so i happily transfer my databases and compiled files over to the new server.
Then i realized the URL is pointed as localhost and this works on local machine which I don't intend to test on the machine but over local network. So my past experience with ASP.Net, i can either connect to the newly setup website using IP address (eg. http://localhost/workflow7 to http://192.168.2.10/workflow7). Well it does show me the login page and after I login into, the unexpected happens. As we are developing in Silverlight and about that's about 90% of our current GUI, it stops working and I got this error, crossdomain error calling webservice which we using to communicate our UI layer with application layer. This is really puzzling as I already have the clientaccesspolicy.xml in my application folder. So I start to google about this and seem this is quite a common issue for Silverlight with web services.
Thus I’m really scratching my head and after intense 1 hour of searching, I found no solutions. I have tried crossdomain.xml after found . But still not working but if I switched back to localhost, then everything works again. This is surely frustrated. But after a good dinner and bath, I try my luck again in Google and i found this excellent article about setting cross domain for Silverlight workaround from Jon Galloway article which pointed me to correct direction about my issue. It got me to Tim Heuer blog about clientaccesspolicy file. I read the whole the article and the last paragraph show my mistakes and it's so plain simple. Let me quote from the site about whereabouts of the file
Root is the word I’m looking for and my file is located wrong place after all. So it should be at the root of the domain and after i copied the file over to my root domain which in this case is the default (wwwroot folder which i think is default folder used by 90% people :-D). My application now is working now. I'm so relieve that I don't have to spend another few hours for this problem. So thanks to Jon and Tim for help me to solve my issue. So anyone else is having this issue? Do leave me a comment if you have similar issues and I see if I can help as well.
Have a nice day!
Then i realized the URL is pointed as localhost and this works on local machine which I don't intend to test on the machine but over local network. So my past experience with ASP.Net, i can either connect to the newly setup website using IP address (eg. http://localhost/workflow7 to http://192.168.2.10/workflow7). Well it does show me the login page and after I login into, the unexpected happens. As we are developing in Silverlight and about that's about 90% of our current GUI, it stops working and I got this error, crossdomain error calling webservice which we using to communicate our UI layer with application layer. This is really puzzling as I already have the clientaccesspolicy.xml in my application folder. So I start to google about this and seem this is quite a common issue for Silverlight with web services.
Thus I’m really scratching my head and after intense 1 hour of searching, I found no solutions. I have tried crossdomain.xml after found . But still not working but if I switched back to localhost, then everything works again. This is surely frustrated. But after a good dinner and bath, I try my luck again in Google and i found this excellent article about setting cross domain for Silverlight workaround from Jon Galloway article which pointed me to correct direction about my issue. It got me to Tim Heuer blog about clientaccesspolicy file. I read the whole the article and the last paragraph show my mistakes and it's so plain simple. Let me quote from the site about whereabouts of the file
"Either way, when you are done with the file, it needs to go in the ROOT of the domain. This is important as it is not the application root, but the root web. Even if your app is at foo.com/myapp, the policy file needs to be at foo.com/clientaccesspolicy.xml."
Root is the word I’m looking for and my file is located wrong place after all. So it should be at the root of the domain and after i copied the file over to my root domain which in this case is the default (wwwroot folder which i think is default folder used by 90% people :-D). My application now is working now. I'm so relieve that I don't have to spend another few hours for this problem. So thanks to Jon and Tim for help me to solve my issue. So anyone else is having this issue? Do leave me a comment if you have similar issues and I see if I can help as well.
Have a nice day!
Posts
