Pet hate - R6034 - Manifest woes

[Stephen Howe]

I keep getting R6034 with MFC executables + DLLs built using VS2005 Professsional

Yet in the linker, Manifests are specified for EXEs (and not for DLLs)
DEPENDS.EXE reveals that the RunTime DLLs appear to be the right ones.

Any suggestions?

Thanks

Stephen Howe

[Stephen Howe]

Well a rebuild all "fixed it".

But I dont wish to rebuild all every time this happens

I wonder if newer VS's are more reliable?

Stephen Howe

[Victor Bazarov]

Post by Stephen Howe
I keep getting R6034 with MFC executables + DLLs built using VS2005 Professsional
Yet in the linker, Manifests are specified for EXEs (and not for DLLs)
DEPENDS.EXE reveals that the RunTime DLLs appear to be the right ones.
Any suggestions?

Have you tried moving to the next compiler (VS2008)? Or the current Beta?

V

[Stephen Howe]

Post by Victor Bazarov
Have you tried moving to the next compiler (VS2008)? Or the current Beta?

No, but we have it installed.
Currently I have major deadline at work where a certain task has to be completed by 1st Jan 2010.

But if we finish early, I do plan to switch all our software to VS2008.
We need to make checks that everything still builds, links & works.
And it maybe that VS2008 C++ will catch some C++ errors that we have overlooked that VS2005 did not.
Each generation round MS's compiler is more stringent, a good thing.

Thanks

S

[Stephen Howe]

Post by Stephen Howe
I keep getting R6034 with MFC executables + DLLs built using VS2005 Professsional
Yet in the linker, Manifests are specified for EXEs (and not for DLLs)
DEPENDS.EXE reveals that the RunTime DLLs appear to be the right ones.

I have just got R6034.
Ran DEPENDS on the executable

Rebuilt the executable from scratch
Ran 2nd copy of DEPENDS on the new executable

They are identical. The RTL is the same.
So I am wondering causes this.

Are incremental links reliable?

S