Activity overview
Latest activity by js_vistadb
OK, I just can't let it go for some reason.... Bugs me when things should work and don't. Using the sxstrace and tracking down the specific file the amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_ca3f79d486b08636.manifest file was corrupt.
I do _not_ normally recommend a user modify these files by hand. After careful consideration and reading through the MSDN I modified mine to the following:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!-- Copyright © 1981-2001 Microsoft Corporation -->
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<noInheritable/>
<assemblyIdentity type="win32" name="Microsoft.VC80.ATL" version="8.0.50727.762" processorArchitecture="amd64" publicKeyToken="1fc8b3b9a1e18e3b"/>
<file name="ATL80.dll" hash="6a91b897f1be0d40f032a8773630c4627cd18bf7" hashalg="SHA1"/>
</assembly>
This fixed my issue. It appears the one on the machine was referencing an ATL version that was not actually installed. I have read where using the default redist in VS 2005 SP1 can cause this issue. I am not sure if Red Gate did this or maybe some other app I use had already done it.
The above build (8.0.50727.762) is the actual build on my machine using the latest VC redirect for VS 2005 today. It appears to work because now my ANTS is working correctly.
I just wanted to follow up in case some other user has the same error. / comments
OK, I just can't let it go for some reason.... Bugs me when things should work and don't. Using the sxstrace and tracking down the specific file the amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0....
Digging further into this particular error it appears that Visual Studio deploys the wrong version of the ATL 8 manifests into sxs under Vista... http://msdn.microsoft.com/en-us/library/ms235624(VS.80).aspx
WARNING: VS2005 SP1 installs some MSM files with version 8.0.50727.42, but builds your code against 8.0.50727.762. WHen you deploy your app on a raw WinXP machine, it gets the 8.0.50727.42 redistributables from the MSMs, which won't work with your installed app.
My workaround is to put the 8.0.50727.762 MSM versions into "C:\Program Files\Common Files\Merge Modules"
Here are some example affected files:
Microsoft_VC80_CRT_x86.msm
Microsoft_VC80_ATL_x86.msm
I still have no idea how you fix a broken side by side for ATL.... / comments
Digging further into this particular error it appears that Visual Studio deploys the wrong version of the ATL 8 manifests into sxs under Vista...http://msdn.microsoft.com/en-us/library/ms235624(VS....
Yes, 4.1 is installed. I had the same error.
I went and attempted to register the profiler core, but I get an error message.
"The application failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail."
That then reveals the following from the event log:
Activation context generation failed for "c:\Program Files\Red Gate\ANTS Profiler 4\X64\ProfilerCore.dll".Error in manifest or policy file "C:\Windows\WinSxS\manifests\amd64_policy.8.0.microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_465807b554eb9197.manifest" on line 1. The manifest file root element must be assembly.
.NET Runtime version 2.0.50727.3053 - Failed to CoCreate profiler.
So this would appear to be a side by side install error caused by the active template library (VC80.ATL). I did see that 4.1 include a new VC runtime redistributable for x64. Maybe that had something to do with it? / comments
Yes, 4.1 is installed. I had the same error.
I went and attempted to register the profiler core, but I get an error message.
"The application failed to start because its side-by-side configuration...
Ants 4 broken on my machine - how to fix?
OK, I have tried this on two machines that I use. Neither one works. ANTS 3 is installed and has run for a long time. Installed ANTS 4 but can't even get the mandlebrot to show times even though...