I found my answer.  Apparently the IDE doesn't halt when placing object's into the ViewState if an error occurs.  Once I figured out it was the ViewState causing the issue, I labeled all the items within my major class as serializable. That cleared up my problem.

---

Ben Santiago, MCP Certified & A+ Certified
Programmer Analyst
(SQL, FoxPro, VB, VB.Net, Java, HTML, ASP, JSP, VBS, Cognos ReportNet)

ViewState requires that all objects placed within it are serialized. If you place an object into the ViewState which is not serializable, then an error will occur. Although you will see the resulting error on your webpage, if you try to run your code in debug mode, a ViewState serializing error doesn’t cause a “halt” in code for you so see where the error is happening.

To fix this problem, you have to update the code of the class/object that you are attempting to store into the ViewState. In the code, you need to flag the class/object as “Serializable”. Be aware that if your class/object has other custom class/object's nested inside it, all the "nested classes" used must also be serializable. Once you have marked every single class associated as serializable, then this error will go away.

Below is a sample of how to do that in both VB.Net and C#.

VB.Net
<Serializable> _
Public Class MyObject
 Public n1 As Integer = 0
 Public n2 As Integer = 0
 Public str As [String] = Nothing
End Class

C#
[Serializable]
public class MyObject {
  public int n1 = 0;
  public int n2 = 0;
  public String str = null;
}

Hope this helped!

---

Ben Santiago, MCP Certified & A+ Certified
Programmer Analyst
(SQL, FoxPro, VB, VB.Net, Java, HTML, ASP, JSP, VBS, Cognos ReportNet)