If I double click on a Visual Studio (VS2017) solution file (*.sln), in Directory Opus 10, VS2017 is launched and it attempts to load my solution file. During the load I get numerous error dialogs including "Unrecognized guid format". I originally thought this was a VS2017 issue, but after much experimenting I have noticed this issue only come up when I double click the SLN file in Directory Opus. If I do this in Windows Explorer all is well. If I launch and load my SLN file using any other means (other than Directory Opus) works well. So I can only assume this is an issue with how DOpus launches applications. Can you please help.
I am also interested in upgrading to the latest version of DOpus, but I want to hold off until I have a resolution to this issue.
We don't have any similar problems launching Visual Studio .sln files from Opus, although we've only tried with current versions of Opus. (Opus 10 is very old now.)
From a quick search, the error you're seeing happens if Visual Studio is configured for compatibility with the wrong Windows OS version. That in turn may be happening because you're launching it from Opus and have Opus itself configured in that way, and Windows is inheriting the compatibility settings from the launching process.
I'd suggest turning off all compatibility settings on dopus.exe and devenv.exe.
Also, Opus should not be run as Administrator (unless UAC is turned off system-wide, of course). Opus should be run at the same elevation level as the rest of the desktop it needs to interact with, with elevation then left to the built-in Admin Mode and UAC support in Opus.
(It's also possible the problem you're seeing is something that didn't work in Opus 10 but already works in Opus 12, due to the many changes over the years. If neither suggestion above works or applies, and you're thinking about upgrading anyway, then it may be worth trying the current version to see if the problem is still there.)