Deployment of application with DLL in Windows 10 in v2.0.1

[moises1953]

Search for DLLs in development and deployment:

In version 1.4 you could declare a DLL simply by name and place it at the executable address, in system32, or at a specified address.

In later versions the IDE has been denying the compilation if the executable is not in QB64, even though the option has been chosen to locate the executables with the sources, and these outside of QB64, which does not seem to be correct.
This is the wiki text: The dynamic library file can be located in the QB64 folder (alongside your programs' .EXE '), in Windows' system32 folder, or in a relative / absolute path specified along with the library name
The consequences that this has in the deployment of an application with DDL's, is that it can no longer be located with the executable, but it can be done:
1. in a QB64 folder, which will have to be created, even if it is not necessary.
2. in system32
3. in a predefined address, for example C: \ AppName, for which it will be necessary to have the same path in the development environment.

Could it be a bug in the IDE?

[moises1953]

I have compiled from the powershell and indeed the compiler does not find a dll declared only by its name if it is next to the executable.
Therefore not that the IDE rejects it, but that the compiler does not find it and the IDE prevents, OK.
It seems ugly to me that an application with its DLL's cannot be deployed in the same folder, whatever it is

[SMcNeill]

Did you click the option to export EXE to source folder?

[moises1953]

Did you click the option to export EXE to source folder?

Yes
And compiling in the powershell with output option has the same result.
C:\qb64\qb64.exe -c D:\QB64F\MeCepWin-F\MeCepWin-B00.BAS -o D:\QB64F\MeCepWin-F\