By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,201 Members | 922 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,201 IT Pros & Developers. It's quick & easy.

...NET..cannot access...msvcr80.dll (missing program file)

P: n/a
Each time I restart computer & run Norton System Works One Button Checkup, it
finds same problems: missing program files: i.e.:
....NET\FRAMEWORK\v2.0...cannot access a necessary file, "msvcr80.dll". I
have .net framework 1.1, .net framework 1.1 hotfix (KB886903), and .net
framework 2.0 installed. I would like to know how to correct the missing
(msvcr80.dll) file problem.
--
Athlon64x2 3800+(2.55 Gh*@1.49v) MSI K8N Neo4 Platinum SLI, 2X74GB Raptors
Raid0, WD2500KS HD, 2X512 MB Crucial Ballistix (2.5-2-2-5 @510DDR 2.85v)
EVGA 6800GT GPU, Enermax 535WPSU, XP pro/XPx64.
Jan 4 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
AMD4me2 wrote:
Each time I restart computer & run Norton System Works One Button
Checkup, it finds same problems: missing program files: i.e.:
...NET\FRAMEWORK\v2.0...cannot access a necessary file,
"msvcr80.dll". I have .net framework 1.1, .net framework 1.1 hotfix
(KB886903), and .net framework 2.0 installed. I would like to know
how to correct the missing (msvcr80.dll) file problem.


This is because the installer for VS.NET 2005 puts unmanaged shared DLLs
in the WinSxS side-by-side cache, and not in %windir%\System32. In a
brilliant flash of inspiration Microsoft decided to call the deployment
unit for shared DLLs a 'shared assembly' and the information that
describes what files that are in such a side-by-side shared assembly
they call a manifest. msvcr80.dll is in a side-by-side assembly called
Microsoft.VC80.CRT, you'll find the DLL under a folder that has this
assembly name in its name under %windir%\WinSxS.

An application that uses a DLL in a side-by-side assembly must have an
application manifest that says the assembleis it uses. If you don't have
an application manifest file (app.exe.manifest for app.exe) then you'll
get the error you mention.

Such a manifest can come through the application manifest file, or if
the module that uses the assembly DLL is itself a DLL then it can be XML
embedded in that DLL.

More details are here:

http://www.grimes.demon.co.uk/worksh...WSThirteen.htm

Richard
--
Fusion Tutorial: http://www.grimes.demon.co.uk/workshops/fusionWS.htm
Security Tutorial:
http://www.grimes.demon.co.uk/workshops/securityWS.htm
Jan 10 '06 #2

P: n/a
Jackpot reply/answer! Thanks much!
--
Athlon64x2 3800+(2.55 Gh*@1.49v) MSI K8N Neo4 Platinum SLI, 2X74GB Raptors
Raid0, WD2500KS HD, 2X512 MB Crucial Ballistix (2.5-2-2-5 @510DDR 2.85v)
EVGA 6800GT GPU, Enermax 535WPSU, XP pro/XPx64.
"Richard Grimes" wrote:
AMD4me2 wrote:
Each time I restart computer & run Norton System Works One Button
Checkup, it finds same problems: missing program files: i.e.:
...NET\FRAMEWORK\v2.0...cannot access a necessary file,
"msvcr80.dll". I have .net framework 1.1, .net framework 1.1 hotfix
(KB886903), and .net framework 2.0 installed. I would like to know
how to correct the missing (msvcr80.dll) file problem.


This is because the installer for VS.NET 2005 puts unmanaged shared DLLs
in the WinSxS side-by-side cache, and not in %windir%\System32. In a
brilliant flash of inspiration Microsoft decided to call the deployment
unit for shared DLLs a 'shared assembly' and the information that
describes what files that are in such a side-by-side shared assembly
they call a manifest. msvcr80.dll is in a side-by-side assembly called
Microsoft.VC80.CRT, you'll find the DLL under a folder that has this
assembly name in its name under %windir%\WinSxS.

An application that uses a DLL in a side-by-side assembly must have an
application manifest that says the assembleis it uses. If you don't have
an application manifest file (app.exe.manifest for app.exe) then you'll
get the error you mention.

Such a manifest can come through the application manifest file, or if
the module that uses the assembly DLL is itself a DLL then it can be XML
embedded in that DLL.

More details are here:

http://www.grimes.demon.co.uk/worksh...WSThirteen.htm

Richard
--
Fusion Tutorial: http://www.grimes.demon.co.uk/workshops/fusionWS.htm
Security Tutorial:
http://www.grimes.demon.co.uk/workshops/securityWS.htm

Jan 10 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.