Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Languages / Managed C++ / March 2006

Tip: Looking for answers? Try searching our database.

Manifest related error on windows xp sp2 machine

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Abubakar - 09 Mar 2006 14:42 GMT
Hi.

I got the following error while running an exe made in visual studio 2k5c++
(all native unmanaged)

---------------------------
Microsoft Visual C++ Debug Library
---------------------------
Debug Error!

Program: D:\Otengo\dlls\winproj.exe

R6034

An application has made an attempt to load the C runtime library without
using a manifest.
This is an unsupported way to load Visual C++ DLLs. You need to modify your
application to build with a manifest.
For more information, see the "Visual C++ Libraries as Shared Side-by-Side
Assemblies" topic in the product documentation.

(Press Retry to debug the application)
---------------------------
Abort   Retry   Ignore
---------------------------

The machine I'm trying to run this on is a windows XP with sp2.

At first I was running this application as a "release" exe with the required
dlls, but the application was crashing. Then I tried to run a debug version
and got the error mentioned above. How do I solve this problem?

Regards,

-Ab.
David Lowndes - 09 Mar 2006 20:24 GMT
>I got the following error while running an exe made in visual studio 2k5c++
>(all native unmanaged)
[quoted text clipped - 7 lines]
>
>R6034

http://msdn2.microsoft.com/en-us/library/ms235560.aspx

Under your VC installation directory, you may find:

%ProgramFiles%\Microsoft Visual Studio 8\VC\redist

and beneath that directories appropriate for your platform.

Copy the appropriate Microsoft.VC80.DebugCRT sub-directory to the
place where your application is so that you get a directory like this:

c:\....\YourAppDir\Microsoft.VC80.DebugCRT

.. and do the same for any other dependent DLLs (MFC maybe)

and then your debug application should run.

Dave
Abubakar - 10 Mar 2006 07:44 GMT
And what about the release application? My main purpose is to run the
"release" build app.

Ab.

> >I got the following error while running an exe made in visual studio 2k5c++
> >(all native unmanaged)
[quoted text clipped - 26 lines]
>
> Dave
Bruno van Dooren - 10 Mar 2006 08:09 GMT
> And what about the release application? My main purpose is to run the
> "release" build app.

with release build you will have to distribute the release runtime dlls or
link against the static runtime libraries.
there is an article about runtime distribution  over here:
http://www.codeproject.com/cpp/vcredists_x86.asp

Signature

Kind regards,
   Bruno.
   bruno_nos_pam_van_dooren@hotmail.com
   Remove only "_nos_pam"

Abubakar - 10 Mar 2006 08:17 GMT
I guess VC\redist\x86\Microsoft.VC80.CRT will help right ?

Ab.

> And what about the release application? My main purpose is to run the
> "release" build app.
[quoted text clipped - 32 lines]
> >
> > Dave
Abubakar - 10 Mar 2006 17:04 GMT
I place these folders there for debug application and it doesnt run.

Ab.

> >I got the following error while running an exe made in visual studio 2k5c++
> >(all native unmanaged)
[quoted text clipped - 26 lines]
>
> Dave
David Lowndes - 10 Mar 2006 20:13 GMT
>I place these folders there for debug application and it doesnt run.

"Doesn't run" isn't very informative.

Do you get any errors messages now?

Dave
Abubakar - 13 Mar 2006 08:15 GMT
Hey the problem is solved. The folder copy that you suggested worked! (Just
so it can help someone in the future I'm writing here what I did):

Dev Environment: I'm running an application that uses WTL for gui, and I'm
building (developing) on visual c++ 2005 (all unmanaged/native) on windows
2000 sp4.

Now I have a fresh "release" build. My "exe" depends on (check through
depends.exe):
1 - cpplib.dll (this is my own dll)
2 - msvcp80.dll
3 - msvcr80.dll

My test machine1 is a new install of windows xp with sp2. The vs.net
installation has never been run on that machine.
I create a new folder (lets call it "testdir") and copy winproj.exe (my
application that I want to test) and cpplib.dll to it. Next I goto:
\Microsoft Visual Studio 8\VC\redist\Debug_NonRedist\x86\
and copy "Microsoft.VC80.DebugCRT" folder to the folder "testdir". So now my
folder hierarchy look like following:
?   cpplib.dll
?   winproj.exe
?
????Microsoft.VC80.CRT
          Microsoft.VC80.CRT.manifest
          msvcm80.dll
          msvcp80.dll
          msvcr80.dll

Now I try to run the winproj.exe and it runs just fine!
Now I want to try this on another test machine that has a never installed
visual studio on it and is running windows 2000. I copy the same folder
hierarchy and the run the exe but it fails to run. Now I change the folder
hierarchy a little bit. What I do is copy every file in the same folder as
my exe file, so the manifest and the dlls and the exe are all at the same
location. Now i try to run the exe and it runs. This hierarchy now also runs
on windows xp. So I have one dsitributeable and any one can xcopy it and
run.

Regards n thanks,

-Ab.

> >I place these folders there for debug application and it doesnt run.
>
[quoted text clipped - 3 lines]
>
> Dave

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.