Re: Error loadin VS 2005 DLLs in Windows Vista
- From: "Patricio" <Patricio@xxxxxxxxxxxxxxxxx>
- Date: Tue, 18 Mar 2008 11:19:52 -0400
I replied directly instead to the group... Here it is.
Thank you Jimi for the information. The technology is very impresive. In
our case the legacy application is already installed ao that I don't know
how it will work deploying our new DLLs using Thinstall. Also, the license
fees per installation is a deal breaker for us, unless it is very afordable,
which I don't espect to be because with a $5000 developer license (which we
need several), and distribution fees that you have to contact them to get, I
expect them to be on the high side.
Anyway, if this issue is not solved by other means I may give a try.
Regards,
Patricio.
"Jimi" <porpoisepower@xxxxxxxxx> wrote in message
news:6d55e95f-5910-4904-a84e-54421213fe45@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Mar 17, 4:15 pm, "Patricio" <Patri...@xxxxxxxxxxxxxxxxx> wrote:
Hello everyone,
We have spend several days trying to make this work to no avail.
The scenario is a Legacy VC 6.0 application which we are adding new mixed
mode DLLs compiled with VS 2005. The Legacy application works fine in
Vista, but we can not make it run when we replace a couple of DLLs with
their VS 2005 version.
1. In Windows XP (with VS2005 installed) the Legacy application ran with
the
VS 2005 DLLs only after we added an application.exe.manifest with the
reference to Microsoft.VC80.CRT. This was the expected behavior.
2. In Vista (Virtual Machine, no VS2005 install to mimic client
configuration) we added the VS2005 DLLs and the manifest and we got error
0xC0150002, which means that Windows was not able to process the
application
binding information.
3. Using the Dependency Walker we see that the VS2005 DLLs have
dependencies
on MSVCR80.dll, MSVCP80.dll, and MSVCM80.dll, which are the correct VS2005
C++ run-time dependencies.
4. Installing the Visual C++ 2005 Redistributable changes the error to:
This
application has failed to start because MSVCR80.dll was not found.
5. Manually copying the MSVC*80 DLLs to System32 generates runtime error
R6034: An application has made an attempt to load the C runtime library
incorrectly, and then we get error 0xc0000142.
I found many post in the internet with the same errors. Some of them have
been fixed by adding the manifest, but we had the manifest all along (even
though
here,http://durgaprasad.wordpress.com/2007/06/04/r6034-c-runtime-error-in-...,
he says that he needed to "touch"the file using the Cygwin tools to force
the metadata to update).
Is there a way to debug/solve this issue? Do we have to go to the Fusion
log? Are we running into UAC issues? We got the same results installing
the new DLLs as administrators. We are using InstallShield 2008 Premier,
but I don't think that is the issue because we get the same results if we
copy the DLLs manually.
Thank you in advance for your time and help. Regards,
Patricio.
Have you tried a "Thinstall Solution"?
If your not familar with the technology, it is a form of
virtualization, that allows you to create a single executable
that has a program and all it's dependencies built into it. It is
wonderful for Distributing Aplications,
and increasing the portability of Apps. A variety of Vendors offer
Thinstall solutions.
LanDesk's solution involves taking pre and post system snapshots,
which are compared, and
an app is compiled from the differences. But you'll need a license
for eachPC that uses a thinstaled app from their.
I've also seen a Package Development Solution (I cannot remember the
vendor), That allowsyou to create Thinstall Executables, and silent
installation apps. By using a thinstalled Ver, you canforce it to use
the working DLL's.
.
- References:
- Error loadin VS 2005 DLLs in Windows Vista
- From: Patricio
- Re: Error loadin VS 2005 DLLs in Windows Vista
- From: Jimi
- Error loadin VS 2005 DLLs in Windows Vista
- Prev by Date: Re: call base class function or derived class function
- Next by Date: Re: CreateThread
- Previous by thread: Re: Error loadin VS 2005 DLLs in Windows Vista
- Next by thread: Trouble with IADs
- Index(es):
Relevant Pages
|
