Skip Navigation LinksHome / Search


Results Per Page

Found 4 results for Issues.
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  Jun 08, 2010 (2 weeks ago)
    Laurent Bugnion has found two issues with Windows Phone 7 ApplicationBar buttons so he wanted to post the workaround he used to make this work.

    The issue here is that pressing a button on the ApplicationBar does not remove the focus from the TextBox where the user is currently typing. If the button is a Save button, this is super annoying: The Binding does not get updated on the data object, the object is saved anyway with the old state, and noone understands what just happened.

    In order to solve this, you can make sure that the Binding is updated explicitly when the button is pressed[...].


  • 0 comments  /  posted by  Silverlight Show  on  Apr 30, 2010 (1 month ago)
    Laurent Bugnion reports a small issue with the release of the Windows Phone Developer Tools CTP (April 2010 Refresh) refresh and gives you an advice how to cope with the problem.

    The issue is that the Expression Blend Add-in Preview for Windows Phone (April Refresh) is not compatible with Blend 4.0.20408.0, which was the public RC (release candidate).

    A few days ago, the Blend team released a fix for an issue that was sometimes causing a crash when Blend was starting up. This new release (V4.0.20421.0) was not very well announced however, and many people (including me) did not install it. After all, Blend did not crash at startup of either of my machines, so I didn’t deem necessary to install yet a new RC.

    However, it is now clear that the Windows Phone 7 Add-In needs this latest-and-greatest version to work. If you have Blend 4.0.20408.0, you won’t be able to work with Windows Phone 7 in Blend.

  • Issues of Silverlight Style System

    0 comments  /  posted by  Silverlight Show  on  Oct 14, 2009 (8 months ago)
    Tags: Styles , Issues
    Alexey Zakharov is asking you for ideas on how to solve some issues of Silverlight style system.

    Styles are not compatible with on demand application loading. Imagine you want to share style dictionary among a set of application modules (something like PRISM module). The source of problem is xaml reader, which parse resource dictionary with shared style. To successfully parse dictionary it requires all controls dll to be loaded. But these controls dll are loaded on demand if module needs them.That is why if you for example load module A which doesn't requires any control libraries, but uses shared style dictionary u will get XamlParseException. We are currently hacking this issue by manual resource dictionary parsing. But it is just another dirty HACK!

  • 0 comments  /  posted by  Silverlight Show  on  Mar 13, 2009 (more than a year ago)
    Tags: .NET , Issues , Solutions

    In his last post, David Anson explained how it was possible for "hidden" event handlers to introduce memory leaks and showed an easy way to prevent such leaks. Now he is going to show how to diagnose a .NET memory leak with the help of WinDbg, SOS, and GCRoot.

    What if you don't know the source of the memory leak in the first place? Knowing how something is leaking is the first step to fixing it, and the web has some great resources for learning more about tracking down managed memory leaks in WPF and Silverlight applications. I am not going to try to duplicate that information here. :) Instead, I'll refer interested readers to these excellent resources and recommend a bit of web searching if additional background is needed.

Help us make SilverlightShow even better. Whether you'd like to suggest a change in the structure, content organization, section layout or any other aspect of SilverlightShow appearance - we'd love to hear from you! Need material (article, tutorial, or other) on a specific topic? Let us know and SilverlightShow content authors will work to have that prepared for you. (hide this)