Have a DLL project associated to a console application in a specified solution.
Initially the DLL was created using files that were added from a location.
These files were removed and the same files that are the source for the console application are the ones for the DLL portion of the project.
Upon compilation, the DLL and the associated object files are stored in a location that is "divorced" from the main solution itself.
The question is....how to update the path for the DLL portion of the project so it can be a part of the same solution?
As well, what does ERROR 48 indicate?
These are two (2) different problems although they may be related?
This MIcrosoft article https://msdn.microsoft.com/en-us/library/7d83bc18.aspx covers the subject. I'm not sure what you mean by adding a PATH setting to the project. If you have a script (e.g. .bat) which you execute prior to using the .dll you might use to modify PATH.
You can't modify PATH in a project.
Which language gave you error 48? From Fortran, that suggests that you're compiling with one version of Intel Fortran but running against run-time DLLs of an older version.
In MS VS, Right-Click on the executable Project and select Properties | Configuration Properties | Debugging | Environment
Do this for each (Debug and Release and ???) configuration.
This will not fix the path if you run the application from the command line (or shortcut).
For running from shortcut, with temporary path, create a batch file that sets the PATH (like above) then executes the appropriate command line.