WPF debug databinding - VS2008 output window has no output when attach to process -

Friends, I'm debugging according to the WPF data binding. I added TraceSources.TraceLevel to the presentation in my xaml.

  & lt; Window â? | | Xmlns: diagnostics = "clr-namespace: System.Diagnostics; assembly = WindowsBase" /> & Lt; TextBlock Text = "{Binding Path = Caption, Diagnostics: Presentation TraceSources.TraceLevel = High}" One ?? | />   
 If I launch the WPF application in my output window by press F5 in VS 2008, I have seen the data binding extension message:  
  System.Windows Data Alert: 47: Binding Experiment (hash = 2520 9 742) has been created for binding (hash = 3888474). System Windows. Data Warning: 91: Binding Expression (hash = 2520 9 742): Get RoutinePropertyInfo (Caption) at Level 0 from Star (hash = 3160 9 76): A ???? a???? System.Windows.Data WARNING: 71: Binding expression (hash = 2520 9 742): Transfer value got a raw value "??? A ???? System.Windows.Data WARNING: 78: Binding Expression (hash = 25209) 742): Using the transfer variable end value ??? A ????   
 But if I run the app directly and add VS 2008 to the process, then the data in the output window There is no compulsive message.  
 Why do I engage in this process to engage Do not see the message? How do these data get binding search messages?  
 (In the production environment, my app has been launched by another XK, and whatever I can do is engage the process ).   
 
 
 This is a complete estimate.  
 When you apply from Visual Studio Let's start F5, there is the console output window, and presumably presenting one definition of TresSources during integration T ConsoleTraceListener is added that can hook up to the Visual Studio Output Console.  
 When you start an application outside of a debugger, it probably can not / can not successfully add a console transparency because there is no one around ... Thus when you debugger your process , WPF data binding trace sources are not redirected in the output window.  
 Perhaps you can add console listeners after they are attached to this process.  
  System.Diagnostics.PresentationTraceSources.Refresh (); System.Diagnostics.PresentationTraceSources.DataBindingSource.Listeners.Clear (); System.Diagnostics.PresentationTraceSources.DataBindingSource.Listeners.Add (New ConsoleTraceListener ()); System.Diagnostics.PresentationTraceSources.DataBindingSource.Switch.Level = System.Diagnostics.SourceLevels.Warning;   
 Finally, ap. The use of conifig was mentioned in the Beta Stolnitz / Costa article so that the output of the text file can be obtained? Is this work?  
 It is worth checking that the system is important. Diagnostics Presentation Terrace Source. Datababing source. After switch.Level you can also attach this process.  
 This comes across a bit more detail on the entire trace source mechanism: