Older versions of windows suffered from dll-hell where different versions of dll's scattered around put programs to a halt with a version of the famous: "Program.exe - Entry Point Not Found. The procedure entry point SomeProcedureName could not be located in the dynamic link library KERNEL32.dll."
Well let me tell you; .net-hell is no better place to stay:-(
We are currently using dephi on two of our development projects. But after delphi started to support .net it's been a hell to install/upgrade.
It'll start with error messages like:
[21D7B652]{dotnetcoreide120.bpl} InteropApp.MSBuildRegisterTaskHost (Line 1350, "InteropApp.pas" + 2) + $40
[5000CC8D]{rtl120.bpl } System.@CheckAutoResult (Line 21634, "System.pas" + 6) + $0
[21D7B652]{dotnetcoreide120.bpl} InteropApp.MSBuildRegisterTaskHost (Line 1350, "InteropApp.pas" + 2) + $40
[21D78232]{dotnetcoreide120.bpl} InteropApp.TInteropHostAppManager.ResolveTempTaskHostStorage (Line 419, "InteropApp.pas" + 5)
and 20-30 lines more
dotnetcoreide120.bpl points me to .net. Standard medicine: Reboot only made things worse, since Eventviewer now fails with the message:
MMC could not create the snap-in. The snap-in may not be installed correctly. Name: Event Viewer. CLSID: FX:{b05566ad-fe9c-4363-be05-7a4cbb7cb510}
The same goes for a few other mmc's like tsadmin.
The first time it happened I was on a brink of restoring the system from a previous backup when I found some changed files under C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG and (since we're using 64-bit win2k8) C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG
We restored machine.config from the backup and it all started working again...
And this after hours of troubleshooting/uninstalling/reinstalling/upgrading .net, and troubleshooting .net is no easy task when sentral pices of the OS like Eventviewer is so dependent of .net.
The lession to learn is to take a backup of your CONFIG folder. It could come handy in a rainy day...
mvh
Ove B-) |
Logg inn
