Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
This should not be the case (i.e "longer and longer env. variables") as installers should *never* change the PATH -- they should just install the required .DLLs in the same directory and/or set the "App Paths" registry keys for the application executable(s) - David "Bruce Hill" <bhill at euphonix.com> wrote in message news:mailman.1038031768.25737.cvsnt at cvsnt.org... > > >In my case only mfc70.dll was missing. Windows would not allow replacement > > >of the other 2 in any case. So my guess is only the mfc70.dll is not copied > > >during install. > > > > > The install doesn't put them in system32, on the > > recommendation/instructions of Microsoft... it relies on the > > installer being able to set a correct path to the cvsnt install > > directory. > > > > The next version will just stuff them in system32 and to hell with it > > (Someone will probably file a bug report about it when I do, too!) > > > > Tony > > Right on! > > Microsoft's recommendations lead to multiple different > copies of dll's. They also lead to longer and longer PATH env > variables which slows the system down. > > - Bruce >