C#

• An opening summary for why developers might value the content.
  
• Your original post at the top.
• See if you/I can talk Colin in to writing the implementation the way he saw to do it. Then dismember his code and place it into yours (in the article text) and any comments he provides.
• Address some of the errors experienced in the appropriate portions of the code with comments.
• In various parts of the article insert in your own feelings and how they changed over time based upon the responses. I don't mean mush feelings I mean ad any knowledge you gleaned and take some guesses at why you think certain parts of your code might have orphaned you.
• I might try on the side to solicit Christian and get his input. I think a collage of experienced feedback throughout the article from people would really spice it up.
• Conclude with your impressions from the feedback and follow-up from the hiring manager. Chalk up a "Lessons Learned Along The Way" type of statement.
  

System.IO.Ports.SerialPort serialPort = new System.IO.Ports.SerialPort();<br />
<br />
:confused:<br />

public static ArrayList SoapDeSerializeArrayList(string Path)<br />
        {<br />
            ArrayList L;<br />
            IFormatter soapFmt = new SoapFormatter();<br />
            Stream s = File.Open(Path, FileMode.Open); //"outfile.xml"<br />
            L = soapFmt.Deserialize(s) as ArrayList;<br />
            s.Close();<br />
            return L;<br />
        }