(X) Hide this
    • Login
    • Join
      • Say No Bots Generate New Image
        By clicking 'Register' you accept the terms of use .

News

Page  
Items View

  • 0 comments  /  posted by  Silverlight Show  on  May 31, 2011 (more than a year ago)
    SilverlightShow Page for all Silverlight and Windows Phone 7 (WP7) things on Twitter

    Barranger Ridler eports an issue when using System Tray and Panorama in Mango.

    Source: 4MK Mobile

    As a developer, the last thing I want to do is take functionality away from users, but in this case, if you’re using a Panorama background image, you have to. The reason I say you have to is that the System Tray won’t overlay over any of your controls, but rather it will take up the top small amount of space at the top of your page pushing everything else down.


  • 0 comments  /  posted by  Silverlight Show  on  Aug 15, 2011 (more than a year ago)

    Read original post by Jeremy Likness at C#er : IMage

    I'm not a big fan of attribute-based validation because I find there are often complex requirements that involve asynchronous operations that often break the attribute model. I prefer more fluent validation using rules that can be shared between the client and server and can handle asynchronous scenarios.
    For those times when I do have to use a class with attribute validations, it doesn't make sense to ignore them and throw in an entirely new model.

  • 0 comments  /  posted by  Silverlight Show  on  Mar 16, 2012 (more than a year ago)

    Read original post at Rockford Lhotka's Blog

    One issue I’ve encountered while building Metro-style WinRT apps on Windows 8 is the need to have my app interact with a WCF service running on the same machine.

    This is obviously a common scenario for any n-tier or SOA app development. The challenge we face is that WinRT apps are blocked from calling back to localhost (127.0.0.1).

  • 0 comments  /  posted by  Silverlight Show  on  Mar 06, 2012 (more than a year ago)

    Read original post at Adam Kinney's Blog

    As a result of the WinJS AppBarIcons post yesterday, I’ve received a fair number of requests asking to see how this compares to what’s available for XAML-based projects. The results are in, but they don’t quite stack up.

    Download the full image

    There are currently 29 options compared to the 150 options in WinJS. Additionally some of the names and icons conflict or are used in different ways. I’m hoping this is ironed out before the full Windows 8 release.

  • 0 comments  /  posted by  Silverlight Show  on  Mar 29, 2012 (more than a year ago)

    Read original post at Johan Laanstra's Blog

    Today I came across an issue with the LongListSelector, part of the Silverlight for Windows Phone Toolkit. Solving the issue seemed pretty simple in the end, but first some background.

    The LongListSelector is a control that can be used to create a list of groups. A good example of this is the contacts list in the people hub. In that list the contacts are organized based on the first letter of their name. Every group contains a header, in this case the first letter, and using this header you can very easily switch between groups. By using the LongListSelector from the toolkit, developers can create the same experiences in their apps.

  • 0 comments  /  posted by  Silverlight Show  on  May 11, 2012 (more than a year ago)

    Read original post by Pratap Lakshman at The Windows Phone Developer Blog

    In an earlier post we looked at how we can gain broad insight into an application scenario’s memory characteristics and how the graph and markers drew our attention to ranges of execution for further analyses. Recall that in the memory leak diagnosis case we chose to analyze only the time range over which we observed the increase in memory usage. Indeed, that is a key first step to the analysis: filtering the memory activity data by a time range. The Heap Summary view is the result of such filtering, and represents the population of the heap during the chosen time range.

  • 0 comments  /  posted by  Silverlight Show  on  May 04, 2012 (more than a year ago)

    Read original post at Sean Sexton's Blog

    Once you spend some time creating a Brush in Blend, e.g. specifying the different colors in a gradient brush, it’s likely that you’ll want to use the same brush in several different spots in your user interface.  You could just copy/paste the definition of the brush in XAML.  But the easier way to reuse a brush is to convert it to a resource and then to reference the resource by name wherever you use it.

  • 0 comments  /  posted by  Silverlight Show  on  Jun 14, 2012 (more than a year ago)

    Read original post by Harikrishna Menon Ajith Kumar at Microsoft Expression Blend Team Blog

    A number of Metro style apps use a hierarchical system of navigation. This is an intuitive and common pattern used by app developers. In this video tutorial, I’ll show you how to style and customize GroupStyles using Blend and VS to implement the hierarchical navigation system.

  • 0 comments  /  posted by  Silverlight Show  on  Sep 06, 2012 (more than a year ago)

    Read the original post by Morten Nielsen at SharpGIS

    Sometimes you have some code that needs to run after a storyboard has completed. In my case I'm working on a little board game, and after each move (which I animate using a Storyboard), I need to figure out the next move, and either start a new play-animation or pass the turn to the other player.

    Therefore I run in a loop until the turn is over. You can detect when a storyboard has finished when the "Completed" event triggers, but that makes for some recursive spaghetti code. It's much easier if I could just "await" the storyboard using a task. So I created the little extension method below that makes this possible. All you have to do to start and wait for the storyboard to finish is:


  • 0 comments  /  posted by  Silverlight Show  on  Jul 14, 2009 (more than a year ago)
    One of the new features that Tim Heuer mentioned in his What’s new/changed post on Silverlight 3 was the fact that any application developer can take advantage of the cached assembly functionality provided by Silverlight. In this post Tim will show you exactly how to do this.

    The assembly caching feature is a cool feature to be able to take advantage of when your architecture makes sense to leverage it.  It isn’t going to be for everyone, but that’s what makes it great – it is an opt-in feature for you as the assembly developer as well as the consumer.  With a few simple steps you can take your Silverlight assembly and prepare it for use on this feature as described above.


Page  

Our News on Twitter