More in this section
Forums / Bugs & Issues / Telerik.Sitefinity.Security.SecurityManager exception after upgrade to .NET Framework 4.7

Telerik.Sitefinity.Security.SecurityManager exception after upgrade to .NET Framework 4.7

The forums are in read-only mode. In case that you want to directly contact the Progress Sitefinity team use the support center. In our Google Plus group you can find more than one thousand Sitefinity developers discussing different topics. For the Stack Overflow threads don’t forget to use the “Sitefinity” tag.
1 posts, 0 answered
  1. Daniel
    Daniel avatar
    0 posts
    22 Jun 2017
    22 Jun 2017
    Link to this post

    Hi, I was trying to run a project when it started a Telerik.Sitefinity Exception (Can see better the attached files) and after some research it seems the reason was because of an upgrade of the .NET Framework to 4.7.

    I saw page in the link  and verified that the problem maybe could be solved by using an internal build or hotfix. I verified that the SiteFinity version is 8.2 and for that reason I decided to use the Sitefinity Internal Build 8.2.5941.0.

    Ialso saw the link and installed the Telerik.Sitefinity.All NuGet package and tried to follow the import steps of the option 2 but I don't what what they mean with "Note the exact build number of the hotfix or internal build".

    Then I tried the approach in and it seems that the internal builds pdbs are being used.

    Then I the the solution build and run the project but without success because it happened the same exception.

    Can anyone please tell me what could be happening? Solutions?

    Thanks for any help!

1 posts, 0 answered