1. On the "Project" tab, in the "Project" group, expand "Import" and select "A .NET assembly".
   
2. In the window that appears, select the .NET assemblies to be integrated into the current project.
   
   • A "Search" area allows you to easily find the desired assembly.
   • The "Select from disk" button allows you to select an assembly that does not appear in the list. The assembly selected via the "Select from disk" button is automatically selected and appears at the top of the list.
   • The "Fill list automatically" button searches for all assemblies available on the computer.
   • New in version 28
     If necessary, specify the targeted .NET framework. The list shows the different Microsoft versions. The "Automatic" option is selected by default.
     Remark: The list of assemblies may vary depending on the targeted .Net framework.
3. Validate. The selected assemblies are imported.

Using elements of the .NET assembly

• Delegates: the delegates can be handled by DotNetDelegate.
  You also have the ability to add a delegate with the += operator:
  clDotNet is ClassEventManagement
  // Branch the event
  clDotNet:m_LogHandler += Proc_Test
  // ...
  // Triggers the event
  clDotNet:SendAMessage("String sent")
  

  //-------------------------------------------------
  // Manage the event
  PROCEDURE Proc_Test(src, args)
  Info("The string passed as parameter via the delegate is " + args:get_Message())
  
• NestedType with more than 1 level
• Reference
• Properties
• Array with more than 1 dimension
• Structures.
• Enums.
  You have the ability to combine the Enum coming from .Net assemblies via &, | , ||, ~ . You have the ability to convert the enums into integers or to build them from integers.
• Internal classes: the following syntax must be used:
  
  <Object name> is "<Class name>"
  
  The syntax without quotes is also available:
  
  <Object name> is <Class name>
  
  Example:
  
  O is "ExternalClass.InternalClass"
  
  
  
  O is ExternalClass.InternalClass
  
• Generic:
  The following syntax is used to instantiate a generic:
  <Object name> is "<Generic name><<Concrete type>>"

  Example for instantiating a generic:
  MyList is "List<CMyObject>"
  
• Generic methods:
  The following syntax is used to call a generic method:
  <Object name>."<Name of generic method><<Concrete type>>"(<parameters>)

  Example for calling a generic method:

  // Prototype of the generic CloneList method of CClone class
  // CloneList(List<T>)
  // ...
  MyList is "List<int>"
  // ...
  clClone is CClone
  MyListCopy is "List<int>" <- clClone."CloneList<int>"(MyList)
  
• Extension methods:
  The extension methods can be called like the methods of the object.

Limitations

• A WLanguage class cannot be derived from a .NET class.
• The following types are supported:
  • Date/Time
  • WINDEV currencies. In output, the WINDEV currencies are converted into decimal numbers.
  • Decimal numbers
    A decimal parameter passed from a .NET assembly to a WLanguage function is converted into currency if possible. If this conversion is not possible, the parameter is converted into double.
  • Structures
• The objects derived in .NET from an exported WLanguage class are not supported. If an object of this type is passed to a WLanguage function as parameter, it is "casted" into the base WLanguage type.
• Passing pointer parameters between WLanguage and .NET is not supported.
• The "structure" members found in classes and/or in sets are not visible in .NET because the WLanguage structures are not visible in .NET. To fix this problem, create a class containing the code of the structure.
• The "class" members found in classes and/or in sets are visible in .NET only if the class is exported as well.
• Caution: Components created with version 11 (or earlier) that use .NET will no longer work with version 28. It is necessary to generate the components again with version 28.

Using standard .NET Framework 4 assemblies (and below)

1. Select the ".NET assemblies" folder in the "Project Explorer" pane.
2. Open the context menu and select "Use a .NET assembly".
3. In the window that appears, click "Automatically complete a list with the .NET assemblies on your disk. Caution: This process may take quite a long time.".
4. Select the standard assemblies to use (mscorlib.dll or another assembly).
5. Validate.

• On the "Project" tab, in the "Project" group, expand "List of elements" and select "List of .NET assemblies used".
• In the "Project explorer" pane, select "List of .NET assemblies used in the project" in the context menu of ".NET assemblies".