This article states the requirements of the .NET Generator requirements for development.
To build .NET applications, you need to install .NET 6.x SDK, which is available here: .NET 6 (LTS).
By default, the .NET generator runs web applications in the Kestrel web server that is included in the .NET SDK. To run the application with IIS working as a reverse proxy in front of Kestrel,
In build time, an internet connection to nuget.org is required in several cases, for example, to get the required version of a DBMS driver.
But in the case of the SAP HANA Database, the required files are not in a NuGet repository, so you must copy to the bin directory the Sap.Data.Hana.Core.v2.1.dll and libadonetHDB.dll files. These files are part of the SAP Hana Client for Windows.
To work with Informix, the DRDA protocol has to be enabled, for this is the one that the driver uses.
1) If .NET 6 SDK is not installed (*), the following error will be displayed:
"error: Dotnet.exe doesn't exist. Install .NET 6."
or, if a previous version of .NET is available, but .NET 6 is missing:
"error: DotNet version >=6 is required. Your dotnet.exe is X.Y.Z. Install .NET SDK"
Note: After installing the SDK, it is necessary to close GeneXus and open it again..
(*) If the error still persists after installing dotnet SDK, check your PATH environment variable. It may be including the dotnet folder at Program Files(x86) instead of Program Files (due to a previous installation of any SDK for x86), so it only sees the installed SDKs for x86. In that case, try removing the wrong dotnet path from the environment variable PATH and restart GeneXus.
2) If DRDA is not enabled in Informix, you may get an error like this
Internal error: Function call failed (ERROR 08001 IBM SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "172.16.0.205". Communication function detecting the error: "connect". Protocol specific error code(s): "10060", "*", "*". SQLSTATE=08001)
The solution is to enable DRDA in the DBMS and set the port number configured for DRDA at the Server TCP/IP Port Property.