Recently I've had a need to include robust and complex math calculations in my c# applications such as polynomial curve fitting, calculus and advanced statistics. I am pleased to say I've found an excellent .NET math code library called NMath from CenterSpace Software. The company is extremely customer friendly, has both email and phone support, and has an easy to use object model. Check them out if you need this kind of functionality.

When developing applications I'm often faced with the decision of whether to develop in LabVIEW or C# since I'm proficient in both. Some of my colleagues have strong opinions about which one is best, or some have expertise in one or the other. I though it may be informative to describe my decision making process when choosing one or the other for a particular application:

• If customer has a particularly strong preference then I go with the language of their choice. Often times this has to do with the skill level in their company in order to allow their ongoing support after I've completed the project. This selection trumps all the others list below.
•  If the application involves multiple buses other that serial, I generally go with LabVIEW since there are just so many already available drivers in the LabVIEW community.
  
• If the application only involves data analysis and, at most, serial communication, I generally go with C#.
• A big advantage of LabVIEW is its extensive library of built in function not always available with C#. So an application requiring one or more advanced functions already available in LabVIEW this favors LabVIEW. However, If I'm coding in C# and I need advanced functionality, I can typically find it in an online post or a third party tool.
• A big advantage of C# is it can provide a much richer user interface and can be more easily be configured to provide a modern user interface. The are also several very good third party feature rich control suites.
• Both LabVIEW and C# have an extensive online presence, both in forums and with MSDN for C# and the national Instruments website for LabVIEW. Extensive coding examples can be found for both languages, and with LabVIEW many examples are provided inside the LabVIEW development environment.
• LabVIEW has an advantage with support since it has both email and phone support.
• Both LabVIEW and C# have good training models, typically online although you can get customer led onsite classes with LabVIEW.

Microsoft provides a basic set of controls in their .NET framework, but for extended functionality and appearance I prefer to use third party controls for my applications. The two I've incorporated are:

• DevComponents DotNetBar Win form control suite - A fairly wide ranging set that includes two of my favorites. The Ribbon control is the easiest ribbon control I found to configure and edit. The other control in this suite I like is the SuperGrid control. It offers an exceptionally easy way to create a mater detail grid.
• SpreadSheetGear - This control provides an on-screen representation of an Excel workbook while not really using the Excel API. This allows placing applications build with SpreadSheetGear to run on a server that does not have Microsoft Excel installed.

I use DataGridView a lot in my C# applications. Why? It provides an efficient way to tabulate and organize data where all rows in a column are of the same data type, like the structure of a database table. For example, a query of a database can be loaded into a .NET DataTable and this can, in turn, be a DataSource for a DataGridView GUI element.