- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In Visual Studio I just stopped being able to debug. It gives the unhelpful message:
Which I would guess means it isn't finding a dll. I suspect libifcoremdd.dll because if I run it in just a standard cmd prompt window that is what happens. But I don't have my standard configuration set to run any particular version because I need to run several. Pretty sure when you pick a version of the compiler to execute in VS it sets the right environment for that compiler. Does it no longer do this when debugging?
Is there a method to see what the environment it is using will be inside visual studio debugging session? I know I could get it from my program, but it won't run.
I don't want to set the PATH to include any specific version.
TIA
Dave
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you try the following. Open project properties. Choose:
Debugging - Merge Environment - No
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well that worked! But I sure don't understand it. The documentation says it controls if the Environment box is added to the system variables. Which I really need it to be. But it is a variable only used by my program so why it would affect the loading of my executable is incomprehensible to me. Any explanations welcome. Also still hoping to understand how to look at the environment without my program loading.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I should have mentioned previously that I had a similar problem, and I found the answer in
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page