Ok guys, I challenge your combined intellects. I have a web application with a silverlight application that calls the ria service. The ria service is defined inside the web application, and everything else is just a dandy.
The problem is this.
I understand that in order for the silverlight application to be able to talk and know what a ria service is, you need to add a link to the service for this service. The service directory defines the ria service and establishes a connection binding. One of the added files is one ServiceReference.ClientConfigthat has a connection binding. During the development of this application, this is how it was configured. And it worked perfectly both locally and on the dev server.
Unfortunately, there were problems deploying to your own client server. At the moment, I participated in other projects, while my employee continued to deploy. Soon he was upset by the stupid mistakes that arose and were gaining some help. This developer came and, although he got his job, but for this he removed the service link from the silverlight project, but left ServiceReference.ClientConfigit that indicated the location of the service in the web application (but what it is, there is no definition or explanation of what the service does, and I'm not sure how the silverlight application should know how to work with it ..). This works fine on my workstation, and he deployed this version to the client server.
When I open a project, it does not start at all. And the reason is that he does not know what the service that I use in the code is. In particular, he does not know where it is (names changed to clarify):
Imports SilverlightApp.ServiceReference.WebApp.Service
I cleaned up the solution, completely deleted and received the latest from the source code, first created a web application and made sure that the asp.net dev server is running, so that the address in ServiceReference.ClientConfigresolved correctly. But alas, he still does not know what it is Imports SilverlightApp.ServiceReference.WebApp.Service.
So, to make it work on my workstation, I added the ServiceReference service, but kept the current connection bindings so that it matches the endpoint in the web configuration of the web application. and changed the import statement to Imports SilverlightApp.ServiceReference, and everything works fine.
What is the reason for this madness?!?!