[Mono-bugs] [Bug 530852] New: [Regression] Debugger won't stop on a break point after the project has been "run remotely"

[bugzilla_noreply at novell.com]

http://bugzilla.novell.com/show_bug.cgi?id=530852


           Summary: [Regression] Debugger won't stop on a break point
                    after the project has been "run remotely"
    Classification: Mono
           Product: Mono: Tools
           Version: MonoVS 0.3
          Platform: i586
        OS/Version: Windows XP
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Visual Studio Integration
        AssignedTo: martin at novell.com
        ReportedBy: twiest at novell.com
         QAContact: mono-bugs at lists.ximian.com
                CC: jpobst at novell.com
          Found By: Component Test


Description of Problem:
If you run a project remotely, and then set a break point and hit "debug
remotely in mono", the debugger won't stop on the break point.

It will stop on the break point if you don't first "run remotely".

This was found in MonoVS 0.3p3.

We used to be able to do this fine before (when we demoed at TechEd, I did this
a lot).


Steps to reproduce the problem:
1. Create a new solution based on the default C# winforms project template
2. Double Click on the form
3. In Form1_Load, add this line:
    Console.WriteLine("Hello World");
4. Click "Mono / Run Remotely in Mono"
5. Choose a host and hit "Ok"
6. Close the app on the Linux side
7. Add a break point in VS to the Console.WriteLine line
8. Click "Mono / Debug Remotely in Mono"
9. Choose a host and hit "Ok"
10. Notice that the debugger doesn't stop on the break point


Actual Results:
The debugger doesn't stop on the break point.


Expected Results:
The debugger should always stop on the break point.


How often does this happen? 
Every time.

-- 
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.