User Tools

Site Tools


namespace_assembly_reference

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
namespace_assembly_reference [2018/09/25 06:01] wolfgangriedmannnamespace_assembly_reference [2020/02/12 05:15] (current) wolfgangriedmann
Line 30: Line 30:
   * either have a using System.IO at the begin of your source or use the full referenced class name    * either have a using System.IO at the begin of your source or use the full referenced class name 
  
-To make it easier for people migrating from VO the development team has added a special mechanism to the X# compiler (this was available also in the Vulcan compiler): an assembly can add an attribute that lists namespaces that should be treated as "implicit". And there is a compiler option that intructs the compiler to automatically add these "implicit namespaces" as using statements to your code.+To make it easier for people migrating from VO the development team has added a special mechanism to the X# compiler (this was available also in the Vulcan compiler): an assembly can add an attribute that lists namespaces that should be treated as "implicit". And there is a compiler option that instructs the compiler to automatically add these "implicit namespaces" as using statements to your code.
 The XPorter automatically enables this option, so you can still use classes like DbServer and DataWindow without including using statements for these classes. The XPorter automatically enables this option, so you can still use classes like DbServer and DataWindow without including using statements for these classes.
 Vn2Ado also uses this mechanism. If you enable this option then you can use the Ado.. classes without extra using statement. Vn2Ado also uses this mechanism. If you enable this option then you can use the Ado.. classes without extra using statement.
  
namespace_assembly_reference.txt · Last modified: 2020/02/12 05:15 by wolfgangriedmann