We develop .xlls (Essentially an Excel Extension in C++) in C++ (Visual studio 2019). We typically debug these by configuring the Debug environment in the properties for the project. We typically set the command to be run as /excel.exe /X and debug the xll code.
This worked fine till we started transition to OFFICE 365. The excel is a 64 bit version. That is really not a problem. We have built appropriate 64 bit xlls. The issue is that Visual Studio fails to launch EXCEL. We see an error "<...>/excel.exe exited with code -1" and a dialog that says could not launch excel.
What has changed? Do folks have similar experience and how have they resolved the issue. The work around is to launch excel from a batch file and attach from visual studio. However this is too tedious.
Thanks in advance for the assistance and help.