Re^2: Problems with FREE MS VC++ tools

[PodMaster]

Actually, the c runtime should always be compatible. Apparently R6034 means the that perl.exe is missing a perl.exe.manifest file, a new feature of XP (starting with msvcr80). So, all he has to do is add a perl.exe.manifest, something like

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
  <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="
+1.0">
      <assemblyIdentity
          processorArchitecture="x86"
          version="5.1.0.0"
          type="win32"
          name="Controls"
      />
      <description>Super wxPerl Application</description>
      <dependency>
          <dependentAssembly>
              <assemblyIdentity
                  type="win32"
                  name="Microsoft.Windows.Common-Controls"        
                  version="6.0.0.0"
                  publicKeyToken="6595b64144ccf1df"
                  language="*"
                  processorArchitecture="x86"
          />
      </dependentAssembly>
      </dependency>
  </assembly>

I'm actually suprised this is the first time he's encountered such an error message.

[JamesNC]

Thanks ++, I created a perl.exe.manifest and put it in the perl bin directory with the changes for my dll minus the publicKeyToken and now the error I get "Access denied", in fact, I can't even run perl unless I remove my entry for the dll.
Update: see above, solution found