Strange MSBuild behavior in Orcas beta 2

After upgrading to Orcas beta 2 from beta 1, I'm constantly getting the following error message after building my WPF (multi-project) solution:

"Entering break mode failed for the following reason: Source file 'XXX.xaml' does not belong to the project being debugged."

This happens only after I clean the intermediate solution folders (bin, obj). When I rebuild the solution twice, this message is no longer displayed.

What can be the cause of this phenomenon? This did not happen previous to beta2.

Cheers,

Yuval

[1000 byte] By [YuvalGilboa] at [2008-1-8]

«« Crystal Report For VS.NET 2005.. Cannot change DBName, ServerName on Runtime if write SQL Statem
»» Determining static classes through reflection

# 1

Moving to the debugger forum, as this is a debugger question I think. (Or maybe WPF?)

DanMoseley-MSFT at 2007-10-2 >

top of Msdn Tech,Visual Studio Orcas,WPF Designer (Cider)...

# 2

VB or C#?

I believe that this is a known issue that was fixed post-Beta2 - let me know whether you are using VB or C# and I'll check

MarkBoulter at 2007-10-2 >

# 3

I am getting this issue in C#, orcas beta 2. I would much appriciate your checking to make sure this issue is resolved.

JohnMelville at 2007-10-2 >

# 4

I too have also been getting this error quite a bit lately in Beta 2 using C#. Unfortunately, this seems to have made it impossible to debug certain pages...

porcus at 2007-10-2 >

# 5

I'm using C#.

YuvalGilboa at 2007-10-2 >

Visual Studio Orcas

WPF Designer (Cider)

Visual Studio Orcas Hot Topic

Visual Studio Orcas New Topic

Visual Studio Orcas

Java / MSDN / Linux Tech / PHP Tech / MSDN DotNet / MSDN TECH / Health Library / Programmers Tech / visual basic Tech / Developer Tech / Ipod faqs / Msdn China Tech