European Experts Exchange (EEE.org) :: Free Experts PHP MySql Oracle Microsoft Web SQL Delphi


Languages :: Csharp :: .Net :: .Net Configuration
By: omuyelijah	Date: 13/06/2007 11:27:14	Points: 20	Status: Answered Quality : Excellent
Hello All, I often have this problem of not being able to run .net applications on systems, on which I later install the framework (2.0). I've read quite enough on using the mscorcfg.msc and have tried configuration, all 2 no avail. Well, I know I am missing something sha but can someone help out? Thanks in advance.
By: omuyelijah	Date: 28/06/2007 17:24:03		Type : Answer
Well, I've been able to resolve the issue after combing some forums, and I share all my experiences here. Let me state firstly that the native assembly cache (i.e. C:\Windows\WinSxS) is not a flop, as I saw someone state in a forum. It really works with the new deployment strategy employed by Microsoft. The error I've been having is simply becos the VC++ application had its manifest file requiring the Microsoft.VC++.DebugCRT libraries (in C:\Windows\WinSxS) of version 8.0.50608.0. whereas the system didn't even have that library installed in the native assembly cache. Even after learning that debug applications should not be redistributed, I rebuilt the application in Release configuration and the library dependence version changed to 8.0.50727.726 but the application failed to work. Now, this is how I got the program to work: 1. Copied the application, its manifest and the Microsoft.VC++.DebugCRT libraries, its manifest files and policies into a folder in a removable drive, attached the drive to the target system and ran the application. Behold, the error message changed to something bearable. 2. To confirm this, I copied the Microsoft.VC++.DebugCRT libraries, its manifest files and policies into the native assembly cache, and then copied only the application and its manifest into the system. On starting the application, the error message changed to something bearable and then I could handle it from there on. Just to be elaborate, this is the error message after steps (1) and (2) above Application failed to initialize properly (0xc00000135). Click on OK to Terminate the application. This error is coming up because there isn't the .NET Framework installed on the target system. So, on installing .NET Framework 2.0, the application started to work well. I add some more things I learnt during this period. - It is possible 4 an application to use a library of a lower version on a system even in the presence of thesame library on the system but a higher version. Visual C++ libraries come with policy files that specify a redirection from a lower version to a higher version. - It is important to consistently update the operating system so that it will provide the system with newer versions for libraries and also give one other tools. - Event viewer can be used to get a clearer view, or obtain more information about errors of the such I encountered. You get to use Event Viewer in Windows (XP) by 1. Start -> Run -> eventvwr 2. Control Panel -> Administrative Tools -> Event Viewer - I suggest that one other way the problem I had could be overcomed is by changing the version of the runtime library specified in the manifest file of the application to the version available in the native assembly cache.

Do register to be able to answer

©2010 These pages are served without commercial sponsorship. (No popup ads, etc...). Bandwidth abuse increases hosting cost forcing sponsorship or shutdown. This server aggressively defends against automated copying for any reason including offline viewing, duplication, etc... Please respect this requirement and DO NOT RIP THIS SITE.
Please DO link to this page! Post to Plurk Post to Yahoo Buzz Post to Delicious Post to Digg Post to MySpace Post to Ping.fm Post to Reddit Post to StumbleUpon

Contact

page generated in 330.797910 milliseconds

Why Google AdSense ads ?

New Improved Search!