Changes between Version 14 and Version 15 of CodeBestPractices


Ignore:
Timestamp:
2012-03-25 20:25:57 (7 years ago)
Author:
jeroens
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CodeBestPractices

    v14 v15  
    33 
    44== Mono compatibility == 
    5 .NET is in theory system-independent, and .NET applications can be deployed under Unix, Linux, MacOS, etc using runtime environments such as [http://www.mono-project.com/Main_Page Mono]. However, not all .NET features work under Mono, most notably the !Microsoft.[wiki:VisualBasic] assembly. This can prove problematic since every Visual Basic project by default receives a reference to this assembly. 
     5.NET is in theory system-independent, and .NET applications can be deployed under Unix, Linux, MacOS, etc using runtime environments such as [http://www.mono-project.com/Main_Page Mono]. However, not all .NET features work under Mono, most notably the Microsoft.!VisualBasic assembly. This can prove problematic since every Visual Basic project by default receives a reference to this assembly. 
    66 
    77In !EwE we have worked around this problem by redefining key types and constants from the Microsoft.!VisualBasic assembly in [http://webservice.ecopath.org/Ecopath/Help/Index.aspx EwEUtils]. You should not use Chr, Asc, IIF, !TriState, !MsgBox, !UBound, !InStr, vbTab, !vbCrLF and a whole whack of other old and familiar constructs if you wish your application to run on any other OS than Windows.