View Single Post
  #45   Spotlight this post!  
Unread 29-04-2012, 21:42
techhelpbb's Avatar
techhelpbb techhelpbb is offline
Registered User
FRC #0011 (MORT - Team 11)
Team Role: Mentor
 
Join Date: Nov 2010
Rookie Year: 1997
Location: New Jersey
Posts: 1,622
techhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond repute
Re: The communication tides are shifting...

Quote:
Originally Posted by MAldridge View Post
To me, the only solution is to scrap the current VB.NET program entirely, and rewrite it from the ground up in a more sensible language like LabVIEW.
Firstly, let me thank you for sharing all that information.

Secondly:
No language insures in the absolute sense you can't have an error at all.

I share some of your lack of enthusiasm personally for .NET languages, however that doesn't mean that I can ignore that a process that produced the buggy product in the first place is prone to be just as buggy on the rebound (pun intended).

If it turns out the that FMS system is quirky they should troubleshoot, repair, replace as necessary.
Reply With Quote