The above code was working fine but yesterday I started getting “the remote server returned an unexpected response : (404)not found”.

Any ideas?

Niyla.

Ps. Also, any chance of doing a web service demo with authentication.

>>Man where is beta 2…???

I heard that Silverlight 2 beta 1 will be available this week
http://michaelsync.net/2008/06/03/news-silverlight-2-beta2-will-be-coming-this-week

Are you at TechEd now? You might already know about that… please share your TechEd exp with me, man how is it over there?

[quote]No. man.. It’s strange that you are missing Cass a lot.. Why not Yasser or Justin or me? hehe [/quote]

I do miss Yasser and Justin (don’t you mean Jason?), but with Yasser, he is working on a large project and he slowly walked away. Jason was very active in SL 1.0 and 1.1, but as soon as 2 showed up, no more. But Imran just vanished from the forum, form other forums, his own blog, no email, nothing. And with Michael, I’m hoping we can get ride of him soon…

>>For me, I more prefer to use Astoria I’m waiting beta2 ..<<
I’m going to TechEd next week and I hope to to find out.

And thanks for info on the service

Mainly, cuz of two reasons..

Reason 1) It’s true that WCF has a lot of cool things but I don’t need them. ASMX Web service works well for me.

The following is a very nice note about WCF from Pete O’Hanlon..

Basically, WCF is a service layer that allows you to build applications that can communicate using a variety of communication mechanisms. With it, you can communicate using Peer to Peer, Named Pipes, Web Services and so on.

You can’t compare them because WCF is a framework for building interoperable applications. If you like, you can think of it as a SOA enabler. What does this mean?

Well, WCF conforms to something known as ABC, where A is the address of the service that you want to communicate with, B stands for the binding and C stands for the contract. This is important because it is possible to change the binding without necessarily changing the code. The contract is much more powerful because it forces the separation of the contract from the implementation. This means that the contract is defined in an interface, and there is a concrete implementation which is bound to by the consumer using the same idea of the contract. The datamodel is abstracted out.

Reason 2) I’m more familiar with ASMX Web Service than WCF since I’ve been using ASMX for 4 years. I played a lit bit with WCF but I don’t have any WCF experience in real projects..

>>I ask this because I’m trying to see if I should only use WCF for SL application services?

For me, I more prefer to use Astoria I’m waiting beta2 ..

>>p.s. Did you hear anything from Imran?

No. man.. It’s strange that you are missing Cass a lot.. Why not Yasser or Justin or me? hehe

I ask this because I’m trying to see if I should only use WCF for SL application services?

Thanks!

p.s. Did you hear anything from Imran?

Funny you wrote this post. I was just reading that post you put on the forum and read what Allan said and I came here to tell you this, but you’re one step ahead of me

Now does that mean for even email we should use SSL? That can get expensive for simple sites?

Man where is beta 2…???

Great Idea. I’ve been thinking about that too.. I asked a questions related to SSL and Silverlight in SL forum but MS guys said that All requests/responses to/from a web service deployed to an SSL secured location are encrypted automatically at the transport layer. So, if we are passing the sensitive data (e.g. credit card or password) from Silverlight to webservice, we don’t need to do anything special. Just configu webservice in SSL and call it from webservice.. that’s all. seems like it’s extremely easy

What do you think?