Hello I do have the simples application of all here is my post asking for guidance on the Silverlight.net forum http://forums.silverlight.net/forums/p/196016/489416.aspx#489416 but now I am thinking that it could be a Winhost related issue how could i fix my issue .. out of the box on Winhost
Omacall33 what exactly is your problem? What is the exact error you are getting and do you have a URL we can look at?
Ria Services Deployment issue Hello Ray here is the link to my App http://www.xneterp.com/medlink/Default.aspx I have tried several ways and Still no luck, the following link should give my patients but it does not http://www.xneterp.com/medlink/Default.aspx#/Patients/WorkWith/PatientsWorkWith I have deployed the SQL database on Winhost, and if I run the application on my localhost IIS but pointing to the remote SQL connection, it works fine. so the remote SQL is fine so then it could be a RIA problem, I have also followed the tips on the following video as well http://channel9.msdn.com/Shows/SilverlightTV/Silverlight-TV-51-Debugging-and-Deploying-WCF-RIA-Services I have spent so many hours on this matter, not even learning Lazy Loading was so hard.. can you please help me
RIA services is very hard to diagnose because of the generic error messages it throws out. You stated that it works on your local computer. First and foremost do not take for granted what assemblies or components you have installed on your local computer. Make sure all these assemblies that you have on your local computer and Bin deployable. This means that you do not have to install it directly on the server but upload the files to your applications Bin directory and your web application should be able to use it. Another common problem with RIA services is the actual connection strings. You maybe using a SQL driver for your connection string that we do not have installed on the server. The best way to troubleshoot this problem is to actually create a simple RIA application. Simply have it query a small database. Set this app as its own unique application folder so it is separated from your main application. The problem with troubleshooting a full application is that there are so many modules, assemblies, and codes it is calling on that it makes it difficult to go through the lines of coding and pin point the root cause of the problem. Making a much smaller and simpler application makes it easier to see where it is going wrong. Lastly, try downloading a software called Fiddler. It is a software you can download and install on your computer for free. What it will do is track all the http calls your browser makes to your web application and depending on where it fails will help you narrow down exactly what part of your web application is actually failing. http://www.fiddler2.com/fiddler2/
