Hi,
Normally, VisualGDB would automatically pick up the deployed file paths, however some projects might be structured in a way that prevents CMake from reporting the correct .so file path to VisualGDB. Please also make sure you are using VisualGDB 5.5 Preview 4, since it includes special checks that normally find and deploy the .so.<version> files automatically.
You can double-check what exactly gets deployed via VisualGDB Project Properties -> Debug Settings -> Verify Deployment Settings.
If you are using the Custom edition or higher, you can use VisualGDB Project Properties -> Custom Debug Steps to deploy arbitrary files before debugging. For lower editions, we would advise experimenting with CMake definition of the libraspicam.so target (e.g. removing the version specifier) to make sure the library path reported by CMake (shown via Verify Deployment Settings) matches the name referenced by the main project.