C#

Pete O'Hanlon wrote:

the only other one I can think of is an OutOfMemoryException.

<br />
try {<br />
   IPerson oPerson = ISession.Get(....);<br />
   ...<br />
   oSomeProperty = LoadProperty(...);    // still okay!! Successfully loaded oSomeProperty and it is not NULL or invalid.<br />
<br />
   oPersom.SomeProperty = null; // Okay!!<br />
   oPerson.SomeProperty = new PersonProperty(...); // Okay!!<br />
   oPerson.SomeProperty = oSomeProperty; // ** crash!!!  oPerson NOT NULL!!<br />
<br />
<br />
} catch(Exception ex)<br />
{<br />
  Console.WriteLine("Tell me everything..."); Exception? try-catch never caught it?!<br />
}<br />
<br />
class Person<br />
{<br />
   protected PersonProperty _SomeProperty = null;<br />
   ...<br />
   public PersonProperty SomeProperty<br />
   { <br />
       get { return _SomeProperty; }<br />
       set {<br />
         _SomeProperty = value; << Actually it crashed right here.<br />
       }<br />
   }<br />
   ...<br />
}<br />

unsafe class Node<br />
{<br />
    fixed (int* ptr = &array[10])<br />
}

8.Kelvin()
{   
  while (!(the machine can program itself))
     Wont_stop_coding = true;
}

class test
{
int Number;
test ref Ptr;
}

josephchild wrote:

and that SQL Server is configured to allow remote connections.

I are troll