1

Closed

GacUtil issue, Prism 4.1

description

After intalling and registering Prism 4.1 I've found that Prism dlls do not listed in "Add Reference.." list filtered by Silverlight 5.
I've registered them by using GacUtil in MSVS 2010 SP1 command prompt:
gacutil /i "C:\Program Files (x86)\Microsoft Prism v4.1\Bin\Silverlight\Microsoft.Practices.Prism.dll"
gacutil /i "C:\Program Files (x86)\Microsoft Prism v4.1\Bin\Silverlight\Microsoft.Practices.Prism.Interactivity.dll"
...
and so forth.
There was message that dll registered successfully for each dll.
However these dlls do not appears in "Add Reference.." list filtered by Silverlight 5.
Then I'm trying to add Microsoft.Practices.Prism.dll in my fresh new SL5 project and getting error message that:
Error 1 Cannot resolve reference assemblies. Please check the reference assemblies. Could not load file or assembly 'System.Windows, Version=5.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e' or one of its dependencies. Не удается найти указанный файл. SilverlightApplication2 E:\Work\Projects\testProjects\SilverlightApplication2\SilverlightApplication2\MainPage.xaml
Currently I'm can't build SL5 projects with linked prism dlls.
Closed Aug 17, 2012 at 6:38 PM by DCherubini
Hi,We are closing this work item as this is probably not an issue in Prism. For more information regarding the topic discussed here, you can check the following thread in the discussions section: - Prism 4.1 & GAC Problem (http://compositewpf.codeplex.com/discussions/391310)Also, for those interested on how to add the Prism 4.1 assemblies to "Add Reference" dialog, please check the following work item: - Bug in RegisterPrismLibrary.proj (Prism v4.1) (http://compositewpf.codeplex.com/workitem/9225)Regards,Damian Cherubinihttp://blogs.southworks.net/dcherubini

comments

usernamed wrote Aug 13, 2012 at 10:31 AM

I was wrong thinking that adding dll to GAC will help to show dll in Add Reference.. list.
I used this to get dll in AddRef list: http://compositewpf.codeplex.com/workitem/9225

But I don't understand why adding dll to GAC led to this issue.
Looks like this is not issue, but rather discussion. Probably, it must be closed.

Sign in to add a comment