 |
|||||||||
|
|||||||||
|
|
I realize that it might be a little early to evaluate the overall experience of doing something like this on a piece of Alpha software, but, I figure if Microsoft is going to assault the developer community with so many betas, alphas, gammas, zetas, and whatever else they can find - its my right as a developer to try out every last one of those products, alpha or otherwise.
First off, it might be worth it to note that there is a Silverlight "Quick Start" for performing this task. The problem is that the Quick Start sucks. It actually tells you to go off and follow the directions for creating a basic ASP.NET Web Service - which is wrong. In order to do this, you need to create a POX service using Orcas, not a WSDL-spewing bloat machine like the default ASP.NET .asmx services.
The key to creating a POX service with Orcas are a couple of attributes that I only wish were available right now in non-Orcas web services. First, you need to decorate your code-behind Web Service class as such:
[System.Web.Script.Services.ScriptService]
Secondly, for each method that you want to be accessible to scripts, you need to configure that method appropriate. It needs the standard WebMethod attribute, but it can also take another one:
[ScriptMethod(UseHttpGet=true)]
This allows your method to be accessed by scripts (no envelopes, just POX), and also informs the web service factory handler that this method is available through HTTP GET requests. At this point, you're probably thinking, "Yay! I've got a POX service!" ... well, almost. Something else that I didn't find in the Quick Starts is that the HTTP POST and HTTP GET protocols are not enabled by ASP.NET web services by default, you have to enable them in your web.config file with the following XML:
<webServices>
<protocols>
<add name="HttpGet"/>
<add name="HttpPost"/>
</protocols>
</webServices>
Now you actually have a POX service that is capable of returning some useful data to your AJAX scripts or, more currently, to your Silverlight Application.
I'll spare you the gorey details of creating the Silverlight application, and creating the ASP.NET "Silverlight link" that will copy the output files of your Silverlight app into your ASP.NET app for building, and just show you the code that I used to consume a simple POX data service method that returns a string. The output of the string is, in typical 'hello world' fashion, used to modify the contents of a TextBlock control:
public void HandleClick(object o, EventArgs e)
{
BrowserHttpWebRequest req = new BrowserHttpWebRequest(new Uri(
"http://localhost/silverdata/dataservice.asmx/GetData?input=test"));
HttpWebResponse response = req.GetResponse();
StreamReader responseReader = new StreamReader(response.GetResponseStream());
string rawResponse = responseReader.ReadToEnd();
Debug.WriteLine(rawResponse);
XmlReader xr = XmlReader.Create(new StringReader(rawResponse));
xr.ReadToFollowing("string");
xr.Read();
labelText.Text = xr.Value;
}
So with all this in place, you can now create your XAML and have something like MouseLeftButtonUp (remember that you don't have Click (yet) in Silverlight..) invoke the POX service, get the data, and then repopulate data elements dynamically at runtime.
The next step here is to obviously do the call to the web service asynchronously (which is entirely possible, and actually pretty easy). I think the next thing I'm going to do as an experiment is to have the code in the Silverlight app modify an HTML element so that it changes to indicate that a data connection is being made in the background. Once the data is retrieved, the HTML element will be set back to normal and the data from the service will be used to populate some controls on the page. We'll see how that turns out :)
