Search

However, as with most things, you can leverage a Silverlight-enabled WCF server to do the dirty work for you. In this steps below I will be showing you the code needed to send the email through the SmtpClient object as well as some minor configurations you need to do to your server to get it working.

There are several different topics I could cover related to "lessons learned" (some of them were more painful than others) but I'll keep it to 5 items for this post and cover additional lessons learned in the future. The topics discussed were put together for a TechEd talk:

1. Pick a Pattern and Stick To It
2. Data Binding and Nested Controls
3. Notify Users of Successes (and failures)
4. Get an Agent – A Service Agent
5. Extend Existing Controls

 

So you want to use OData but you need to secure the data? There are a ton of ways to do this, but this covers a simple way using ASP.NET Forms Authentication.

This is a follow-up to the previous Blog (http://openlightgroup.net/Blog/tabid/58/EntryId/99/Simple-Silverlight-4-Example-Using-oData-and-RX-Extensions.aspx) where we looked a simple Silverlight application that talks to an oData service.

As with the last tutorial, we will not use a database, just a simple collection that we are creating programmatically. This will allow you to see just the oData parts.

When communicating in a .NET to .NET messaging scenario then optimizing the data contracts is an additional way to reduce the SOAP message size. This together with binary encoding will reduce the message size about 4 times. Especially looking to the Windows Phone 7 development this will help much when the traffic goes over a low bandwidth network like GSM or UMTS.

Silverlight has been around for quite some time now and I hope most of you who have been working on Silverlight 3.0, might have started migrating to Silverlight 4.0. As you are aware, Silverlight is now used for developing LOB applications where the requirement is to develop loosely coupled browser based applications using Silverlight. One of the approaches here is to remove the dependency between Model  and View (UI) so that they can be developed and tested independent from each other. This article shows how to create a Silverlight application that consumes a WCF service keeping minimum dependencies between the Model and View

If you’re building Silverlight applications that consume data then you’re probably making calls to Web Services. We’ve been successfully using WCF along with Silverlight for several client Line of Business (LOB) applications and passing a lot of data back and forth. Due to the pain involved with updating the ServiceReferences.ClientConfig file generated by a Silverlight service proxy (see Tim Heuer’s post on that subject to see different ways to deal with it) we’ve been using our own technique to figure out the service URL. Going that route makes it a peace of cake to switch between development, staging and production environments.

Unfortunately there is no way to accomplish this directly from Silverlight. It is also not supported via JScript so communicating between Silverlight and JScript will also not help here.

The first way I have found to accomplish this is to have your Silverlight application communicate directly with a WCF service where the web services returns to the Silverlight client the IP address of the client.

There are scenarios where Silverlight client calls WCF (or REST) service for data.

Now, if the data is cached on the WCF layer, the calls can take considerable resources at the server if NOT cached. Keeping that in mind along with the fact that cache is an cross-cutting aspect, and therefore it should be as easy as possible to put Cache wherever required.

From our Silverlight application we must be able to view documents. Documents are stored in an existing document management system and are accessible through a WCF REST service. It sounds very easy, but it was quite hard to understand all the stuff going on behind the Internet Explorer and the Microsoft Office.