I figured out what my problem was. I will explain what happened so that someone else that might have this same issue will know how to fix it. However, I must make one comment. Regarding your suggestion about make "Link with runtime packages" false. This is great if you have a single DLL or no DLLs a...

I looked at your post and considered the information. In the test case that I sent, it has both the DEBUG and RELEASE builds. The DEBUG build uses "static" linking for the DLLs, and the RELEASE build uses "dynamic" linking for both DLLs. The problem still occurs whether you use "static" or "dynamic"...

I thought about it and figured the quickest way to get this fixed is to provide you with a test case. I have created one for you. It has two DLLs and an EXE. The DLLs are very simple and use TeeChart. TeeChart is dynamically linked. When I run the exe, the exception occurs. If there is only one DLL,...

I think you might have missed what I said in the original post, but I will clarify. It is not a single project I am migrating but a group of them. I have a project group that contains many projects. The main processing consists of 17 DLL projects along with the main EXE project. The EXE uses all 17 ...

I just installed C++ Tokyo Update 1. This is the first time I have used Tokyo as the base release had too many issues for me to migrate from Berlin. I have installed the latest 2017.22, updated my project files, and compiled all my DLLs and EXEs. When I run the EXE, I get the message "raised excepti...