(X) Hide this Join our next live webcast on December 15th, 10 am PDT - Building a Silverlight 4 application end-to-end. Presenter: Gill Cleeren
Check the webinar agenda | Register for the webinar
Skip Navigation LinksHome / Search


Results Per Page

Found 4 results for Error Handling.
Date between: <not defined> and <not defined>
Search in: News , Articles , Tips , Shows , Showcase , Books

Order by Publish Date   Ascending Title   Rating  

  • 0 comments  /  posted by  Silverlight Show  on  Aug 18, 2010 (3 months ago)
    In this blog post, Vincent Leung explains what causes and how to avoid the following error - "The remote server returned an error: NotFound".

    Have you seen this error message before?  “The remote server returned an error: NotFound.”, Not particularly helpful! This is your Silverlight app’s way of telling you that there was an exception during a WCF Service call. You can fix this with a little WCF server-side magic.  The magic is described in the Silverlight documentation in an entry called Creating and Handling Faults in Silverlight.

  • Data Validation And Templating in Silverlight 4

    0 comments  /  posted by  Silverlight Show  on  Jul 26, 2010 (4 months ago)
    In the fifth part of his series on Templates and DataValidation, Jesse Liberty is creating an application that demonstrates how to modify the Visual State for invalid data. 

    In this first approach, we’ll create the MVVM project as well as the editing form and we’ll populate it with data from an object.  To get started, open Expression Blend 4 (or Visual Studio 2010)  and select MvvmLight (SL4)  Name the project Validation and make sure Language is set to C# (or VB if you are transposing) and the Version is set to 4.0.  Click OK.

    Jesse's previous posts you can find here:

    • Visual State Manager A-Z
    • Styles (followup)
    • Templates, Visual State and Fun With Controls
    • Teaching An Old Control New Tricks With Templates
  • 3 comments  /  posted by  Silverlight Show  on  Jun 22, 2010 (5 months ago)
    Mads Laumann got this error in a Silverlight 4 project and after he googled it for some time without any luck, he decided to write a quick blog post just to help others which might have the same problem.

    Today I got this error “XAML Namespace http://schemas.microsoft.com/expression/blend/2008 is not resolved.” in a Silverlight 4 project. I happened right after I added some VisualStates in Blend 4. I could remove the VisualState XAML and everything would then build again fine. As meantioned I googled the error but couldn’t find a solution.

  • 0 comments  /  posted by  Silverlight Show  on  Nov 23, 2009 (more than a year ago)
    In this blog post Jeff Handley focuses on the DomainDataSource error handling story.

    The biggest problem was when errors occurred during Load() or SubmitChanges(), server-side errors would be silently swallowed unless you opted into the LoadError, LoadedData, and SubmittedChanges events, and explicitly checked for errors.  With the PDC release, we've change this behavior, among others related to error handling.