468,291 Members | 1,489 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,291 developers. It's quick & easy.

"The system cannot execute the specified program"

Hi,

I installed Visual Studio 2005 SP1, my application does not start on
machines without Visual Studio installed any more. It was working without
SP1.

After searching the web, it seems caused by manifest file, I changed link
option to generate external manifest file. The manifest lists dependency to
two version of CRTs, is that the problem and why it lists both?

Thanks,

Chris

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">

<dependency>

<dependentAssembly>

<assemblyIdentity type="win32" name="Microsoft.VC80.DebugCRT"
version="8.0.50727.762" processorArchitecture="x86"
publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>

</dependentAssembly>

</dependency>

<dependency>

<dependentAssembly>

<assemblyIdentity type="win32" name="Microsoft.VC80.DebugCRT"
version="8.0.50608.0" processorArchitecture="x86"
publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>

</dependentAssembly>

</dependency>

</assembly>
Jan 12 '07 #1
2 14573
Chris wrote:
Hi,

I installed Visual Studio 2005 SP1, my application does not start on
machines without Visual Studio installed any more. It was working without
SP1.

After searching the web, it seems caused by manifest file, I changed link
option to generate external manifest file. The manifest lists dependency to
two version of CRTs, is that the problem and why it lists both?

Thanks,

Chris

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">

<dependency>

<dependentAssembly>

<assemblyIdentity type="win32" name="Microsoft.VC80.DebugCRT"
version="8.0.50727.762" processorArchitecture="x86"
publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>

</dependentAssembly>

</dependency>

<dependency>

<dependentAssembly>

<assemblyIdentity type="win32" name="Microsoft.VC80.DebugCRT"
version="8.0.50608.0" processorArchitecture="x86"
publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>

</dependentAssembly>

</dependency>

</assembly>

What is your projetc type?
C/C++ or pure dotnet(C#,VB.NET)?
If pure dotnet app(C#,VB.NET), only the dotnet framework is necessary. I
think you are not in this case.

If C/C++ app, take care the VS2005 sp1 update some C/C++ runtime
libaries, e.g. the "msvcrt80.dll".
If your app links with the dll version C/C++ runtime, you need to deploy
the new C/C++ DLLs also.

--
Jacky Kwok
jacky@alumni_DOT_cuhk_DOT_edu_DOT_hk
Jan 15 '07 #2
On Jan 12, 3:33 pm, "Chris" <chrisfo...@newsgroup.nospamwrote:
Hi,

I installed Visual Studio 2005 SP1, my application does not start on
machines without Visual Studio installed any more. It was working without
SP1.

After searching the web, it seems caused by manifest file, I changed link
option to generate external manifest file. The manifest lists dependency to
two version of CRTs, is that the problem and why it listsboth?

Thanks,

Chris

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">

<dependency>

<dependentAssembly>

<assemblyIdentity type="win32" name="Microsoft.VC80.DebugCRT"
version="8.0.50727.762" processorArchitecture="x86"
publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>

</dependentAssembly>

</dependency>

<dependency>

<dependentAssembly>

<assemblyIdentity type="win32" name="Microsoft.VC80.DebugCRT"
version="8.0.50608.0" processorArchitecture="x86"
publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>

</dependentAssembly>

</dependency>

</assembly>
I have this same problem. Did you ever find a solution?

Feb 28 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

145 posts views Thread by Sidney Cadot | last post: by
19 posts views Thread by Neil Cerutti | last post: by
reply views Thread by NPC403 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.