Beta 2: Entering break mode failed for the following reason
Here is the message box:
Microsoft Visual Studio
Entering break mode failed for the following reason: Source file 'f:\WpfApplicationDebug\WpfApplicationDebug\Window1.xaml' does not belong to the project being debugged.
Usually, this condition occurs when the project was not rebuilt prior to starting the debugging session, when the assembly file for the project is out of date, or when the project source files were moved to a different disk location between the time the project was built and the debugging session was started.
Edit and Continue will be disabled for this debugging session.
OK
I tried to create the simplest application.
Here is the Window1.xaml:
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:l="clr-namespace:WpfApplicationDebug"
xmlns:s="clr-namespace:System;assembly=mscorlib"
Title="Window1" Height="300" Width="300">
<Window.Resources>
<s: String x:Key="message">
Hello, World!
</s: String>
<l:DebugConverter x:Key="debugConverter"/>
</Window.Resources>
<Grid>
<TextBlock Text="{Binding Source={StaticResource message}, Converter={StaticResource debugConverter}}"/>
</Grid>
</Window>
and the only code:
...
{
#region IValueConverter Members
public object Convert(object value, Type targetType, object parameter, System.Globalization.CultureInfo culture)
{
return value;
}
public object ConvertBack(object value, Type targetType, object parameter, System.Globalization.CultureInfo culture)
{
return value;
}
#endregion
}
...
I get the message box above when i put a breakpoint on Convert method. "value" is right. Everything looks fine except the message box before breaking. Application runs as expected, but I cannot be sure of that.
I am actually trying to write a relatively complex code with attached properties and markupextensions and there is something going strange there. I thought I would ask before blaming my code
BTW I thought silverlight tools might have caused these and repaired the visual studio installation without any luck.
// Edit
I forgot to mention that a breakpoint on InitializeComponent(); breaks without any message.
