You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the screenshot, Module1.vb is shown as unsaved, despite having been recently built and executed. Since the wrong code compiled and ran, breakpoints were not hit and the debugger terminated (ran to completion) without having the chance to evaluate the expected local variables.
Expected Behavior:
Unsaved files are saved before building a project.
Actual Behavior:
Unsaved files are not saved before building, and stale code is executed without any warning to the user.
The text was updated successfully, but these errors were encountered:
Version Used: 5f72d78
Steps to Reproduce:
Integration test for showed this error when building the above commit.
In the screenshot, Module1.vb is shown as unsaved, despite having been recently built and executed. Since the wrong code compiled and ran, breakpoints were not hit and the debugger terminated (ran to completion) without having the chance to evaluate the expected local variables.
Expected Behavior:
Unsaved files are saved before building a project.
Actual Behavior:
Unsaved files are not saved before building, and stale code is executed without any warning to the user.
The text was updated successfully, but these errors were encountered: