Hi all,
I have this application that apparently depends on the Visual Basic RunTime 5 dll "MSVBVM50.dll" . Although the dll is captured during the install of the application, and is part of the project, the resulting virtual app won't run, unless this dll is also copied to the base.
I noticed that the virtual app wouldn't run on a clean system, but would run on the system that was used to capture the installation (and has all the relevant files in the base). After that, I was able to pinpoint the problem to this one dll.
Although it is easy enough to put this dll in the base, or write a script that copies the dll to the base on runtime, it is more important for me to know what's going on. Why isn't ThinApp able to use the virtual instance of this .dll. It is part of the project in the directory %SystemSystem% and is included in the build. Why does the virtual app need it in the base as well?
One possible explanation is that the application has something done by another process that is part of the base. This process would need the dll to be in the base, as it can't see the virtual filesystem. Is there a way to check this?
Has anyone seen this before? Any suggestion is welcome!
Thanks,
Vincent