Welcome Guest! To enable all features please Login or Register.
Options
View
Go to last post Go to first unread
Offline tdsbarchitect  
#1 Posted : Monday, August 28, 2017 8:28:25 AM(UTC)
tdsbarchitect


Rank: YAF Forumling

Reputation:

Joined: 8/21/2017(UTC)
Posts: 3
Canada


We are in the process of upgrading to the latest version of YAF in our DNN 9 environment. In our previous YAF installation (1.9), we did not sign the YAF assemblies because we have other unsigned DLLs in our environment that made it difficult for us to use the YAF signed assemblies. When we upgraded YAF in our DNN environment and used the unsigned assemblies recently, we received the following error:

Could not load file or assembly 'YAF.Core, Version=2.2.4.2, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required. (Exception from HRESULT: 0x801310

We think this might be due to other new signed assemblies used by YAF, but are not fully sure which ones are causing the problem. All of the System DLLs are signed, but they didn't cause a problem when we were using unsigned YAF DLLs before. AutoFac and CookComputing were also previously signed and didn't cause a problem. There are a number of new DLLs being referenced that we are wondering about. We managed to find unsigned versions of the ServiceStack and Farsi DLLs and are using them, but it didn't resolve the issue. We were not able to find an unsigned version of the OMU.ValueInjector 2.2.3.2 DLL and are still looking for it.

Does anyone have an idea about how we can use the unsigned version of the YAF DLLs without having this issue? Is there any way to globally remove the strong named assembly validation checking to avoid this error?
Sponsor
Online tha_watcha  
#2 Posted : Tuesday, August 29, 2017 1:28:53 AM(UTC)
tha_watcha


Rank: YAF.NET Project Lead

Reputation:

Medals: Medal of Honor: Portal Puzzle Master: Portal Puzzle Master for DNNMedal of Honor Key: Given to pillars of the community who are key players in the YAF community and project.DNN Master: DNN Module ManBug Killer Medal of Honor: Medal for being a kick-ass bug killer!Medal of Honor for the Support King: Support King! Amazing asset to the YAF.NET Community.

Joined: 3/6/2010(UTC)
Posts: 3,730
Germany

Thanks: 70 times
Was thanked: 1148 time(s) in 978 post(s)
As far as i can see the only dll from yaf that is not signed is the Yaf.DotNetNuke.Module.dll. all other dlls are signed. this was also the case in the past? is it possible that in the past you manually compile YAF and remove the signing?
Rss Feed  Atom Feed
Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Notification

Icon
Error