API Set Resolution may loop back to module being loaded

There is a case where a DLL’s API Set reference may resolve to the original DLL. An example is Kernel32.dll!InitializeProcThreadAttributeList, which forwards to api-ms-win-core-processthreads-l1-1-0.InitializeProcThreadAttributeList, which resolves back to Kernel32.dll!InitializeProcThreadAttributeList. This causes the API Set to not actually resolve and results in an error when attempting to call the function that was searched for.

[TheWover]

@ElephantSe4l Fixed in latest version.

[djhohnstein]

To reproduce:

1. Download the dev branch zip file
2. Change the project properties to a Console Application, .NET 4
3. Add the following Program.cs to your project:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;

namespace DInvoke
{
    class Program
    {
        public static void Main(string[] args)
        {
            IntPtr fn = DynamicInvoke.Generic.GetLibraryAddress("kernel32.dll", "InitializeProcThreadAttributeList");
        }
    }
}

1. Run the application on x64 Server 2012 R2 instance. The application will bomb out on L627 of DynamicInvoke/Generic.cs as shown:

As a workaround, I used GetModuleA and GetProcAddress to get the address of InitializeProcThreadAttributeList