(X) Hide this Watch a recording of the live webcast '10 Silverlight Tips' by Gill Cleeren, delivered on October 27th.
Skip Navigation LinksHome / Search

Search

 
Results Per Page

Found 3 results for Mads Laumann.
Date between: <not defined> and <not defined>
Search in: News , Articles , Tips , Shows , Showcase , Books

Order by Publish Date   Ascending Title   Rating  

  • How your designer can try your Windows Phone 7 game

    0 comments  /  posted by  Silverlight Show  on  Oct 04, 2010 (1 month ago)
    Mads Laumann found a way for the designers to try Windows Phone 7 games.

    Source: Laumania.Net

    We are two developers and one designer doing a Windows Phone 7 game in XNA. The developers can of course try the game all the time in the emulator that VS2010 deploys the game to, the designer is more tricky. Our designer of course needed to be able to try out the game from time to time, but he doesn’t know anything about “getting latest” from source control or building the code in VS2010.
    So what do we do?



  • 0 comments  /  posted by  Silverlight Show  on  Aug 02, 2010 (3 months ago)
    Mads Laumann found out that the TreeViewDragDropTarget doesn’t have an “EnableDragDrop=true/false” property and decided to show you how to enable / disable the drag’n’drop mechanism.

    I’m recently worked on a project where I needed this property. At least I needed to be able to toggle drag’n’drop on and off depending on some conditions in the application. So here is how I did it.

  • 3 comments  /  posted by  Silverlight Show  on  Jun 22, 2010 (4 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.