Today me and my colleagues tried to install a web application contructed under .RETARD (Micro$oft call it .NET), but not using Web Deployment Projects and Setup Projects as usually the installations are done. Instead, the client requested a precompiled site install through site building.
Everything goes ok, untill we reach the old installation directory deletion. The first Micro$oft Wintendo Server 2003 appeared:
Well, the IIS is stopped, the system it’s up to date with the latest service patch (Micro$oft call it service pack) and updates and no time to search for known bugs in the Micro$oft Knowledge Base.
The folder is empty too. No way, begin the installation…
If the application works, and .RETARD holds the assemblies in the bin folder, the .RETARD framework is installed and everything seems to be ok, we get the next error message:
Some question arround this error:
- Why are the assemblies copied to the bin folder if .RETARD don’t use them?
- Why the error message suggest you to run regedit and don’t to run a propper configuration wizard as Micro$oft easy to use policy claims?
- Why isn’t a relevant source line, but know exactly which assembly fails to load and is refered in the configuration file?
- Why do I must tolerate these errors, if the site is compiled and ready to use?
I still can’t understand how many people is still using this kind of trash software…
