After some problems with a previous VS.NET 2003 module project, I have restarted and created a module from scratch (CodeSmith, etc.)

My module successfully adds records to the database, but, for some reason, it does not work when I navigate to an existing record in the edit screen and try to update/change a record via the Update function and stored proc. It doesn't blow up, it shows no error in the log viewer...but when I carefully watch it in my debugger, I notice that right at the end it says "thread being aborted" in the try/catch block.

private void cmdUpdate_Click(object sender, EventArgs e)

{
try{
if (Page.IsValid == true)
{

MultiSectionInfo objMultiSectionInfo = new MultiSectionInfo();
objMultiSectionInfo = ((MultiSectionInfo)CBO.InitializeObject(objMultiSectionInfo, typeof(MultiSectionInfo)));
objMultiSectionInfo.ItemId = itemId;
objMultiSectionInfo.PortalId = PortalId;
objMultiSectionInfo.ModuleId = ModuleId;
objMultiSectionInfo.LinkTitle = LinkTitle.Text;
objMultiSectionInfo.SectionTitle = SectionTitle.Text;
MultiSectionController objCtlMultiSection = new MultiSectionController();

if (itemId == -1 || Null.IsNull(itemId))
{
objMultiSectionInfo.CreatedDate = DateTime.Now;
objCtlMultiSection.Add(objMultiSectionInfo);
}

else
{
objMultiSectionInfo.CreatedDate = DateTime.Now;
objCtlMultiSection.Update(objMultiSectionInfo);
}

//try{  THIS TRY/CATCH WAS AN ATTEMPT TO FIX/FIND THE REAL PROBLEM

Response.Redirect(Globals.NavigateURL(), true);

//}catch (ThreadAbortException ex){Thread.ResetAbort();}

catch (Exception exc)
{
Exceptions.ProcessModuleLoadException(this, exc);
}

Change

Response.Redirect(Globals.NavigateURL(), true);

to

Response.Redirect(Globals.NavigateURL(), false);

so DotNetNuke can finish it's processing.  Your code is having a control on the page try to end the current thread immediately, and DotNetNuke needs to finish and clean up first.  Use the later to avoid the ThreadAbortException.

Aaron