A
Alban
Folks,
I have 2 versions of my application, say MyApp.exe (v1.0) and
MyApp.exe(v2.0)
Both are VB6 applications. V1.0 is deployed with PDW (VB installer)
and V2.0 is deployed with Installer1.1.
These 2 products must co-reside on a PC and use shared files.
Problem: I remove from my PC a shared file and when I launch MyApp.exe
v1.0, it launches the resiliency process associated to MyApp.exe v2.0
!
If I rename myapp.exe v1.0 or if a change its location on the PC, the
repair process for v2.0 still launches !! Why is that ? How can the PC
associate myapp.exe v1.0 deployed with PDW, with MyApp.exe v2.0
deployed with MSI.??
I have 2 versions of my application, say MyApp.exe (v1.0) and
MyApp.exe(v2.0)
Both are VB6 applications. V1.0 is deployed with PDW (VB installer)
and V2.0 is deployed with Installer1.1.
These 2 products must co-reside on a PC and use shared files.
Problem: I remove from my PC a shared file and when I launch MyApp.exe
v1.0, it launches the resiliency process associated to MyApp.exe v2.0
!
If I rename myapp.exe v1.0 or if a change its location on the PC, the
repair process for v2.0 still launches !! Why is that ? How can the PC
associate myapp.exe v1.0 deployed with PDW, with MyApp.exe v2.0
deployed with MSI.??