Make Net c# DLL and call

[boludoz]

using System.Runtime.InteropServices;

namespace dllSource
{
    public class Operation
    {

        [ComVisible(true)]
        public int Add(int x, int y)
        {
            int z;
            if ((x == 10) && (y == 20))
            {
                z = x + y;
            }
            else
            {
                z = x;
            }
            return z;
        }
    }
}

 

Local $aResult = DllCall("HelloWordDll.dll", "str", "Operation", "int", 2, _
                "int", 1)
ConsoleWrite("Error : " & @error & @CRLF)
ConsoleWrite("Result : " & $aResult & @CRLF)

Hello, can someone explain to me how to call this DLL, or how to call it, or how to fix the DLL, I'm new to C# but I know it's possible.

Edited May 16, 2022 by boludoz

[RTFC]

Local $aResult = DllCall("HelloWordDll.dll", "int:cdecl", "Add", "int", 2, _
                "int", 1)
ConsoleWrite("Error : " & @error & @CRLF)
if IsArray($aResult) Then ConsoleWrite("Result : " & $aResult[0] & @CRLF)

Untested (never used C# in my life; not going to either). Calling convention is cdecl; you return an int, not a string. AutoIt DllCall func returns an array if successful. Check that you compile as dll (not as exe!) and with the correct bitness (x86 vs x64).

EDIT: Never mind; my suggestion would work with C++, not C#.

Edited May 16, 2022 by RTFC
clarifications & typos

[boludoz]

53 minutes ago, RTFC said:

Local $aResult = DllCall("HelloWordDll.dll", "int:cdecl", "Add", "int", 2, _
                "int", 1)
ConsoleWrite("Error : " & @error & @CRLF)
if IsArray($aResult) Then ConsoleWrite("Result : " & $aResult[0] & @CRLF)

Untested (never used C# in my life; not going to either). Calling convention is cdecl; you return an int, not a string. AutoIt DllCall func returns an array if successful. Check that you compile as dll (not as exe!) and with the correct bitness (x86 vs x64).

Sorry, I can't figure out how to find the function I'm calling, thanks, there must be something in my compiler.

[Danyfirex]

You can't do it that way.  You would need to register a COM then use ObjCreate. You can use C# using CLR. check DotNet.

 

Saludos

[LarsJ]

The AutoIt DllCall() function can only be used to execute functions in dll-files implemented in unmanaged languages such as C, C++ and Pascal. The DllCall() function cannot be used to execute functions in .NET assembly dll-files implemented in managed languages such as C#, F# or VB.NET.

With an AutoIt background, the DotNetAll.au3 UDF as implemented in Using C# and VB.NET Code is by far the easiest way to execute C# or VB.NET code directly within an AutoIt script.

This is a slightly simplified version of the C# code. COM visibility is handled by the DotNetAll.au3 UDF. Test.cs: 

using System;

public class Operation
{
  public int Add(int x, int y)
  {
    int z;
    if ((x == 10) && (y == 20))
    {
      z = x + y;
    }
    else
    {
      z = x;
    }
    return z;
  }
}

And the AutoIt code. Test.au3: 

#AutoIt3Wrapper_Au3Check_Parameters=-d -w 1 -w 2 -w 3 -w 4 -w 5 -w 6 -w 7

#AutoIt3Wrapper_UseX64=Y

Opt( "MustDeclareVars", 1 )

#include "DotNetAll.au3"

Example()

Func Example()
  ; Create $oOperation object
  Local $oNetCode = DotNet_LoadCScode( FileRead( "Test.cs" ), "System.dll" )
  Local $oOperation = DotNet_CreateObject( $oNetCode, "Operation" )

  ; Now the Add() function can be executed
  Local $z = $oOperation.Add( 10,  3 )
  ConsoleWrite( "$oOperation.Add( 10,  3 ) = " & $z & @CRLF )

  $z = $oOperation.Add( -5, 20 )
  ConsoleWrite( "$oOperation.Add( -5, 20 ) = " & $z & @CRLF )

  $z = $oOperation.Add( 10, 20 )
  ConsoleWrite( "$oOperation.Add( 10, 20 ) = " & $z & @CRLF )
EndFunc

Run the AutoIt code in SciTE with F5. The C# code doesn't need to be registered. Output in SciTE console: 

$oOperation.Add( 10,  3 ) = 10
$oOperation.Add( -5, 20 ) = -5
$oOperation.Add( 10, 20 ) = 30

The benefits of the DotNetAll.au3 UDF are:

• The .NET source code can be easily written in SciTE without the need for a specific development tool
• The .NET code is compiled and executed directly in your AutoIt script, where you apply the code
• If the AutoIt script is run in SciTE with F5, .NET error messages appear in the console
• The .NET code can be easily distributed in the form of source files (text files)
• You avoid the registration/unregistration tyranny of .NET assembly dll-files

Another way to execute C# code is briefly described in this post. This method requires an IDE to compile the C# code into a .NET assembly dll-file and it requires the dll-file to be registered/unregistered.

All required code is contained in the 7z-file:
Operation.7z

Edited May 17, 2022 by LarsJ

[pixelsearch]

@LarsJ we missed you.
Glad to have you back after 4 months and let's hope everything is alright for you 

[boludoz]

7 hours ago, LarsJ said:

The AutoIt DllCall() function can only be used to execute functions in dll-files implemented in unmanaged languages such as C, C++ and Pascal. The DllCall() function cannot be used to execute functions in .NET assembly dll-files implemented in managed languages such as C#, F# or VB.NET.

With an AutoIt background, the DotNetAll.au3 UDF as implemented in Using C# and VB.NET Code is by far the easiest way to execute C# or VB.NET code directly within an AutoIt script.

This is a slightly simplified version of the C# code. COM visibility is handled by the DotNetAll.au3 UDF. Test.cs: 

using System;

public class Operation
{
  public int Add(int x, int y)
  {
    int z;
    if ((x == 10) && (y == 20))
    {
      z = x + y;
    }
    else
    {
      z = x;
    }
    return z;
  }
}

And the AutoIt code. Test.au3: 

#AutoIt3Wrapper_Au3Check_Parameters=-d -w 1 -w 2 -w 3 -w 4 -w 5 -w 6 -w 7

#AutoIt3Wrapper_UseX64=Y

Opt( "MustDeclareVars", 1 )

#include "DotNetAll.au3"

Example()

Func Example()
  ; Create $oOperation object
  Local $oNetCode = DotNet_LoadCScode( FileRead( "Test.cs" ), "System.dll" )
  Local $oOperation = DotNet_CreateObject( $oNetCode, "Operation" )

  ; Now the Add() function can be executed
  Local $z = $oOperation.Add( 10,  3 )
  ConsoleWrite( "$oOperation.Add( 10,  3 ) = " & $z & @CRLF )

  $z = $oOperation.Add( -5, 20 )
  ConsoleWrite( "$oOperation.Add( -5, 20 ) = " & $z & @CRLF )

  $z = $oOperation.Add( 10, 20 )
  ConsoleWrite( "$oOperation.Add( 10, 20 ) = " & $z & @CRLF )
EndFunc

Run the AutoIt code in SciTE with F5. The C# code doesn't need to be registered. Output in SciTE console: 

$oOperation.Add( 10,  3 ) = 10
$oOperation.Add( -5, 20 ) = -5
$oOperation.Add( 10, 20 ) = 30

The benefits of the DotNetAll.au3 UDF are:

• The .NET source code can be easily written in SciTE without the need for a specific development tool
• The .NET code is compiled and executed directly in your AutoIt script, where you apply the code
• If the AutoIt script is run in SciTE with F5, .NET error messages appear in the console
• The .NET code can be easily distributed in the form of source files (text files)
• You avoid the registration/unregistration tyranny of .NET assembly dll-files

Another way to execute C# code is briefly described in this post. This method requires an IDE to compile the C# code into a .NET assembly dll-file and it requires the dll-file to be registered/unregistered.

All required code is contained in the 7z-file:
Operation.7z

With the greatest respect and admiration for your work, that statement is not correct, AutoIt can execute DLLs made in the net framework, and I can tell because I've seen it.

P.S, I loved your solution so much that I'm going to mark it. What you did is a work of art!

Edited May 17, 2022 by boludoz

[argumentum]

3 hours ago, boludoz said:

AutoIt can execute DLLs made in the net framework, and I can tell because I've seen it.

Cool, so, can you post code to show how is done straight from AutoIt ?

Edited May 18, 2022 by argumentum
can't remove the link =/

[jchd]

6 hours ago, boludoz said:

AutoIt can execute DLLs made in the net framework

Please post a proof of concept!

[boludoz]

14 hours ago, jchd said:

Please post a proof of concept!

 

16 hours ago, argumentum said:

Cool, so, can you post code to show how is done straight from AutoIt ?

Using this, https://sites.google.com/site/robertgiesecke/Home/uploads/unmanagedexports

https://github.com/3F/DllExport

Unfortunately I don't know much about DLL and C#.

For example:

class Test
{
  [DllExport("add", CallingConvention = CallingConvention.Cdecl)]
  public static int TestExport(int left, int right)
  {
     return left + right;
  } 
}

The other way would be with a kind of wrapper.

Edited May 18, 2022 by boludoz

[jchd]

Yes you can use the nuget package and restrict your C# to (more or less) C-compatible code, but still without #-style marshalling, overloading or recursion.

At this point you'd rather just produce the DLL from plain C.