If you can’t attach the debugger to a Silverlight application opened in new browser window using HtmlPage.Window.Navigate method then do the following:

1. Go to Debug –> Attach to Process
2. In Attach to Process dialog select process which host Silverlight application
3. Click on “Select…” button under “Attach to:” section
4. In Select Code Type window select “Debug this code type” option and uncheck all checkboxes except Silverlight
5. Click OK –> Attach

Uhh, it's a hot day: first the visual studio 2010 beta 2 has came out and now JetBrains released first public available build of the ReSharper 5.0 :)

Here is download page: http://www.jetbrains.net/confluence/display/ReSharper/ReSharper+5.0+Nightly+Builds

What's New in ReSharper 5.0

• External Sources
• Structured Patterns
• Project Refactorings
• Call and Value Tracking
• Internationalization
• Visual Studio 2010 support (coming soon)
• ASP.NET markup support
• ASP.NET MVC support
• Intellisense improvements
• Bookmarks
• Inspect project/folder
• Upgrade-to-LINQ analysis
• Native NUnit support
• Xml Formatting

Here you could find more info about R# 5.0 futures: ReSharper 5.0 Overview

Hi all,

it is my first post and I'd like to strat it from a small trick for defining value converters in app.xaml file in silverlight project.

Problem:

If you define Converters in app.xaml (see below) then you find that Visual Studio designer fails to render User Controls (Visual Studio designer become blank).

<Application xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"

             xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"

             xmlns:myconverters="clr-namespace:MyCustomConverters;assembly=
                        MyCustomConverters"

             x:Class="ConverterInAppXaml.App"> 

    <Application.Resources>

        <ResourceDictionary >

            <myconverters:MyCustomTextConverter x:Key="myTextConverter"/>

        </ResourceDictionary>

    </Application.Resources>

</Application>

Upd: not the converter defenition in app.xaml file cause the visual studio designer to go blank but xmlns defenition.

Solution:

To avoid this designer problem move namespace declaration closer to usage:

<Application xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"

             xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"

             x:Class="ConverterInAppXaml.App"> 

    <Application.Resources>

        <ResourceDictionary xmlns:myconverters="clr-namespace:MyCustomConverters;
            assembly=MyCustomConverters">

            <myconverters:MyCustomTextConverter x:Key="myTextConverter"/>

        </ResourceDictionary>

    </Application.Resources>

</Application>

Voila!!! now designer work perfect and able to render our content.