.NET Generator Standard Classes - FAQ

Official Content
This documentation is valid for:

Here are some frequently asked questions about GeneXus .NET Generator Standard Classes.

1. Where are Standard Classes downloaded from?

Whenever a .NET Generator Environment in a Knowledge Base is built for the first time, a set of standard classes are copied from the NuGet cache to the web\bin directory. This cache is populated with NuGet packages published in different cloud repositories. .NET Standard Classes in particular are published in two repositories: nuget.org and Azure packages. Both repositories are configured in the NuGet.config file in the Model directory. For example, at C:\Models\TestKB\NETSQLServer\NuGet.Config. As described in https://docs.microsoft.com/en-us/nuget/consume-packages/configuring-nuget-behavior, the feeds in NuGet.Config are added to the ones in user NuGet.Config.

To get the list of local caches, use this command:

dotnet nuget locals all --list

Output example:

http-cache: C:\Users\<user>\AppData\Local\NuGet\v3-cache
global-packages: C:\Users\<user>\.nuget\packages\
temp: C:\Users\<user>\AppData\Local\Temp\NuGetScratch

To clear all the NuGet package caches (the three directories in the previous example), use the following command:

dotnet nuget locals all --clear

2. How can the version of the Standard Classes of a generated application be found?

The version used is specified in the file Directory.build.props located in the model directory; for example, C:\Models\TestKB\NETSQLServer\Directory.Build.Props and it is the same as the value of the Standard classes specific version property.  Directory.build.props is a known mechanism to customize the build process; for example, by defining global properties for projects (*.csproj) in any subfolder.

3. Build Error: NU1102: Unable to find package GeneXus.Classes.Web.Core with version (= 1.28.5)

When an invalid version (1.28.5 in the example error) is specified in the Standard classes specific version property, this error is printed in the build output. In that case, change the version property to a valid number. The list of available version numbers can be obtained as described in Standard classes specific version property or browsing GeneXus.Classes.Core package versions.


Since GeneXus 17 Upgrade 11.

See Also

Deploy to GeneXus Prototyping Cloud: under the hood (FAQs)