Menu
I was stepping through the debugger in some website database code, and ended execution before the database changes were applied. But they were still written to the database!
I tried to recreate the problem using a Windows Form application, and it didn't write to the database (expected behaviour). I went back to the website, and it did.
Here is a simple example page. I am running this in a web site if it makes a difference:
<%@ Page Language="C#" %>
<%@ Import Namespace="System.Diagnostics" %>
<!DOCTYPE html>
<script runat="server">
protected void Page_Load(object sender, EventArgs e)
{
using (MsSqlDataContextDataContext db = new MsSqlDataContextDataContext())
{
Product product = db.Products.First(p => p.id == 21);
Debug.WriteLine("Line 1");
// I learnt the hard way that if you try to update the database with the value
// that already exists, it seems to get optimised away.
// The update must a new value.
product.Type = "bogus" + DateTime.UtcNow.Ticks;
Debug.WriteLine("Line 2"); // <- Breakpoint here
db.SubmitChanges();
}
}
</script>
<html>
<head runat="server">
</head>
</html>
I end execution (Shift+F5) at the breakpoint, before the second debug print or SubmitChanges() get executed. "Line 2" is not output to the debug window, but the database changes are made.
Running the same test in a Windows Form does behave the same.
Is the page life-cycle, or session management somehow interfering here? How is this even possible, Line 2 doesn't get printed!
554
When you stop debugging in the winform app, the process is terminating and your code stops executing.
In asp.net this is not the case. When you stop the debugger (usually) it won't terminate the iis process, just detach the debugger. Your code continues running and the request completes.
There are duplicates for this question, have no rep to mark this as duplicate.
75
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
