A conundrum with remote databases and web services

General question: can anybody think of the most likely reason for this problem (running under Visual Studio 2008 Professional, C#):?

I wrote a database program using Siliverlight and using Linq-to-SQL in C# and it worked fine in localhost. It employed various WCF web services as well.

I ported this program from localhost to a remote host, including the MS SQL Server 2008 database the program depends on.

MOST of the WCF web services work exactly as before--most, but not all. MOST of the program runs exactly as before, even though it is remote--most but not all. Hence this question.

A few WCF web services will not work (you get obsure errors, apparently originating remotely).

If I switch back to localhost, the errors disappear.

But again, not all web services have this error.

My suspicion: I think certain DLLs were 'corrupted' in the transfer from local to remote. Rebuilding the web services does not help. I think I'll have to rewrite from scratch the web services affected.

The connection strings were 'globally' changed (using web.config file).

Does this problem ring a bell? Please answer so that future viewers can learn. I don't think I'm the only one.

I will post more as I learn more, but I just want to start the thread.

Like I say, certain WCF web services work, others don't. Perhaps the .DMBL drag-and-drop database relationship file was geared (internally) to the local database, and now that the database is remote it causes problems? But why for certain web methods and not for others? As far as I can tell they are identical. Besides, the connections strings were "globally" changed from local to remote database (via Web.config) so that should not matter.

I personally think it's a "bug" in Visual Studio 2008.

 

...There are a few guys here who have gone through that WCF hoop.
Hopefully one of them will see this and respond.
All the best,
Mark

 

Post the exact error messages you are getting. Also read this post and let us know what you see. http://blog.discountasp.net/how-to-troubleshoot-silverlight-ria-applications/

 

Thread closed: trivial mistake on my part

I solved this problem. It was a trivial mistake on my part: the database I was using in my program was slightly different than the earlier database I had attached to DASP--an extra table was added in the new database. Once I reattached the new database in DASP, using this thread: http://support.discountasp.net/KB/a188/sql-2008-management-tools.aspx , the program worked since it had the correct remote database.

A trivial mistake on my part, nothing to do with DASP.

All's well and DASP rocks!

 

...Good job.
Ride safe ;-)