A
Admiral Habor
Guest
Hi,
I have a native C++ program which works fine when started outside of Visual Studio.
If I start it as debug or release build from within Visual Studio it crashes the moment a special third-party dll gets loaded.
This dll is not intentionally loaded but comes in as a system dll the moment I open a FileDialog (via IFileDialog).
If I remove the program (OldNewExplorer) which registered this dll to the system the starts from within Visual Studio work, too.
Is there a way to tell Visual Studio not to debug or ignore a third-party dll coming in via system?
Undid Iridium
Continue reading...
I have a native C++ program which works fine when started outside of Visual Studio.
If I start it as debug or release build from within Visual Studio it crashes the moment a special third-party dll gets loaded.
This dll is not intentionally loaded but comes in as a system dll the moment I open a FileDialog (via IFileDialog).
If I remove the program (OldNewExplorer) which registered this dll to the system the starts from within Visual Studio work, too.
Is there a way to tell Visual Studio not to debug or ignore a third-party dll coming in via system?
Undid Iridium
Continue reading...