A new assembly directory will be added for each CLR version (see reference [1][2] for details). This is to save older application due to breaking changes in assemblies of newer CLR. So if you are running an application with CLR 2, it will look into GAC of CLR 2 and CLR 1.1 but it will not in assembly of CLR 4.0.
As current GACBrowser version (1.0 or lower) is older than CLR 4.0, it cannot display assemblies of CLR 4.0. But it will display assemblies for .NET version 2.0 and CLR 1.1.
Next version of GACBrowser (4.0.0 to align with CLR version 4.0) which will be release by mid of this September will have support for viewing and deleting assemblies of CLR version 4.0.
Reference:
1. http://stackoverflow.com/questions/2660355/net-4-0-has-a-new-gac-why
2. http://msdn.microsoft.com/en-us/magazine/dd727509.aspx
UPDATE: THIS IS DONE: http://gacbrowser.blogspot.com/2011/01/gac-browser-and-remove-10-release.html
As current GACBrowser version (1.0 or lower) is older than CLR 4.0, it cannot display assemblies of CLR 4.0. But it will display assemblies for .NET version 2.0 and CLR 1.1.
Next version of GACBrowser (4.0.0 to align with CLR version 4.0) which will be release by mid of this September will have support for viewing and deleting assemblies of CLR version 4.0.
Reference:
1. http://stackoverflow.com/questions/2660355/net-4-0-has-a-new-gac-why
2. http://msdn.microsoft.com/en-us/magazine/dd727509.aspx
UPDATE: THIS IS DONE: http://gacbrowser.blogspot.com/2011/01/gac-browser-and-remove-10-release.html
1 comment:
I am extremely busy :( will update this ASAP after 18th November, 2010
Post a Comment