If you want to have resources in your PBD or EXE that are automatically located at run time, you cannot even use relative folders like "./Resource/xxxx.yyy" for example. The resource must be treated as local. For example: "XXXXX.png". Then including these in a PBR would work 100% so that you do not have to deploy the sub-folder(s) with your EXE.
Once you get into large production Apps though, PBD & DLL files are definitely the way to go. Otherwise, your PBR setups can be quite complicated. Also, to maintain as well.
what is exactly the problem with relative resource-paths in the PBR? We have restructured our workspace and moved all resources into a subfolder "resource".
The PBR look like this: resource\save.ong resource\load.png
The pictures are defined in the source code like this "resource\save.png". All works fine when we compile that PBR into our resource.pbd, no image needs to be deployed.
That does not work for me.
However, if I place the resource PBL in the same "resource" folder with no paths in the PBR. That links all the external resources properly into a PBD which works at deployment time. I just copy the resource PBD to the main EXE deployment folder. If I do it your way, I need to deploy the "resources" folder along with the EXE.