|
Hi Mike, Heat runs but many of our DLLs in our
product have a manifest in them indicating this dependency. I noticed
that we have at least a dozen DLLs with manifests requiring VC80.CRT"
version="8.0.50608.0 but the pop-up error saying it cannot find
MSVCR80.DLL only comes up 4 times. Maybe it is something else. We are not trying to include the Visual C
Runtime in our package. How would we ignore this dependency from
Heat? A pop up appears requiring user intervention and I am running heat
from a perl script so as to have the build be automated. We are shipping a copy of the JRE we are
using and when heat gets to those DLLs it causes a pop up 7 times indicating “Java
Plug-in 1.5.0._07 is not installed properly”. I actually have this
version of JDK installed on my system and use it with my IDE’s and
Tomcat. Do I need the path to these DLLs in the system’s path for
heat not to complain? From: Mike Dimmick
[mailto:[EMAIL PROTECTED] Sorry, I was assuming that the problem
was that heat.exe wouldn't run because MSVCR80.DLL was missing, but I see that
Heat is a .NET Framework executable. I have to assume that you're trying to
include the Visual C Runtime in your package. You should ignore this dependency
from Heat. The supported method of redistributing
the VS2005 C runtime within an MSI is to use a <Merge> element to
merge in the Microsoft_VC80_CRT_x86.msm merge module. -- Mike Dimmick From: Steven
Chin [mailto:[EMAIL PROTECTED] I checked and I do have that policy file
and but I don’t think the redirect is working. <bindingRedirect
oldVersion="8.0.41204.256-8.0.50608.0"
newVersion="8.0.50727.42"/> heat still cannot find MSVCR80.DLL. From: Mike Dimmick
[mailto:[EMAIL PROTECTED] Yes, it does indeed do this. However,
you should have a publisher policy installed on your machine which redirects to
8.0.50727.42. I also have one which redirects to 8.0.50727.163. I'm running
Windows XP SP2 with all current patches. Look in
%SystemRoot%\WinSXS\Policies\x86_policy.8.0.Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_x-ww_77c24773
and check that 8.0.50727.42.policy is present, and that the corresponding .cat
file is also present. If not, reinstall the vcredist package. You can't just
copy MSVCR80.DLL - you must use an installer which correctly installs the Win32
assemblies. -- Mike Dimmick From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Steven Chin Visual Studio 2005 Released version 8.0.50727.42 creates
output DLLs with a manifest that says it depends upon <assemblyIdentity
type="win32" name="Microsoft.VC80.CRT"
version="8.0.50608.0" Thus, heat can never find the MSVCR80.DLL version on the
machine. Is there a way to make heat ignore the version dependency so as
to take the latest version which is on the machine? Alternatively,
is there a patch to VS 2005 to create correct manifest that indicates the
correct version of VC80.CRT that it is using instead of a beta 2 version? |
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
