If you try to run an MSVC console app and get an error like this:
This application has failed to start because msvcp80d.dll was not found. Re-Installing the application may fix this problem.
What can you do to fix this situation?
(Don't tell me to buy a Mac, please).
Go buy a new television.
It might not fix your problem, but at least you'll have a new PC.
I would check the internet to see what the file is exactly and then, probably, reinstall the program. If it's part of the OS, I would check for viruses, and then, you will probably have to reinstall the OS.
Google had a lot of answers:
http://forums.microsoft.com/msdn/showpost.aspx?postid=72965&siteid=1
Grubau....in the living?
Buy a Mac.
Quotegrimw wrote:
Buy a Mac.
yeah, pry wouldn't be a bad idea ;-)
QuoteCrashenX wrote:
QuoteBuy a Mac.
;-)
and then run into 50 other problems trying to use your MS program on the mac
and living quite well might I add.
good to hear
It has something to do with the manifest of your program... If I remember correctly... I had this problem a while ago when I switched from .net 2003 to 2005. There should be support on how to fix this known bug on MSDN. This link might help if you can decipher the MS BS. ;-) Hope this helps.
http://msdn2.microsoft.com/en-us/library/ms235624(VS.80).aspx (http://msdn2.microsoft.com/en-us/library/ms235624(VS.80).aspx)
I've never crossed that specific problem, but if i'm 'missing' a .dll. I usually track it down on the CD or wherever I can find it, and plug it in to the right directory (or reinstall). This usually occurs from either a bad installation (i.e. corrupted file on installation disc, etc) or malicious programs on your computer.
This was the first hit on Google, and it looked like it addressed the problem.
Link to MSDN forums on the specified problem (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=15218&SiteID=1)
Though I'm sure the OP knows all this (beings as who they are ;-) )
If that doesn't work, go kick Jeff. He'll fix it or beat you into submission. :lol:
Quotemy_handle wrote:
QuoteCrashenX wrote:
QuoteBuy a Mac.
;-)
and then run into 50 other problems trying to use your MS program on the mac
Actually, Windows XP, VS, etc run on my MacBook just like they do on my home computer. Fine. Of course, I know my system and know how to address the problems that occasionally occur. I'll tell you something about my MacBook though. Never have I installed Windows XP so easily. Parallels setup is amazing. (Oh and 0 problems running my MS programs on my Mac).
Oh, and for the record:
OSX is a better OS than Windows. :innocent:
QuoteI switched from .net 2003 to 2005
Ooooh. If you installed VS .net 2005 on a system that had 2003 w/out completly uninstalling 2003. That right there may be your problem.
You're probably right but everthing works fine now :-D