Oleksii Samokhval (Customer) asked a question.

May 20, 2025 at 2:27 PM
NuGet Packages conflict during the upgrade proccess

Hello,

I'm trying to upgrade from Sitefinity 15.2.8422 to 15.3.8521 using Sitefinity CLI. However, the upgrade fails due to a NuGet dependency conflict:

  • Progress.Sitefinity.Headless v15.3.8521 requires System.Runtime.CompilerServices.Unsafe = 6.1.0
  • System.Memory v4.6.3 (required by the CLI upgrade process) requires System.Runtime.CompilerServices.Unsafe >= 6.1.2

As a result, the upgrade cannot proceed using standard tools like Install-Package or the CLI itself.

Please advise on how to resolve this issue, or whether a fix or guidance will be provided in an upcoming patch.

Thank you!

  • 12 answers
  • 343 views

  • Oleksii Samokhval (Customer)

    Thank you for your response. I upgraded the Sitefinity CLI to the latest version you mentioned, and it resolved the issue. I’ll proceed with testing now.

  • Michael Grady (Partner)

    Running into this issue with the latest version of the CLI built from source

    • Jonathan Read (Progress Software)

      @Michael Grady (Partner)​ ensure you have the latest version or use the release assets (my preferred way). If that doesn't help or you are sure you are on latest sf version ... Pay attention to when visual studio open and runs the nuget install (package manager) I had a machine in the past that did not use "All" for the package source and it cause similar issues to what you all are reporting. If you can change it to all before the commands are run i believe it might fix the issue. I never found fix for the issues and have a new machine so I forgot about it.

      • Michael Grady (Partner)

        grabbed the release assets, and yanked any other package source other than all out of VS and its still stuck with the same basic error (slight differences)

         

        Update-Package : Unable to find a version of 'System.Runtime.CompilerServices.Unsafe' that is compatible with 

        'Microsoft.Bcl.Cryptography 10.0.0 constraint: System.Runtime.CompilerServices.Unsafe (>= 6.1.2)', 

        'Microsoft.Bcl.Memory 10.0.0 constraint: System.Runtime.CompilerServices.Unsafe (>= 6.1.2)', 

        'Microsoft.Extensions.Primitives 10.0.0 constraint: System.Runtime.CompilerServices.Unsafe (>= 6.1.2)', 

        'System.Diagnostics.DiagnosticSource 10.0.0 constraint: System.Runtime.CompilerServices.Unsafe (>= 6.1.2)', 

        'System.Memory 4.6.3 constraint: System.Runtime.CompilerServices.Unsafe (>= 6.1.2)', 'System.Text.Json 10.0.0 

        constraint: System.Runtime.CompilerServices.Unsafe (>= 6.1.2)', 'System.Threading.Tasks.Extensions 4.6.3 constraint: 

        System.Runtime.CompilerServices.Unsafe (>= 6.1.2)'.

         

         

        I have tried going to the latest version of 15.3 form the 15.2 version I'm on to the highest version of 15.4, and so far same result.

      • Michael Grady (Partner)

        cache clearing didn't help, and I removed the other sources from the project's nuget config.

         

        What seemed to have allowed things to attempt to move along is by hand force installing certain package versions such as tuple. I'm not ruling out that its not some custimizations to the project and the packages added for them, but the errors are useless to narrow down what is causing the issue. Like the error above, they all wanted unsafe 6.1.2, nothing wanted lower... so how is it getting suck

      • Michael Grady (Partner)

        I think there needs to be testing to go from 15.2 to anything higher. Can't try to walk to 15.3 then 15.4 because the cli wants to install 15.4 headless. Headless seems to have a missmatch of .unsafe (headless = 6.1.0 and everything else wants unsafe 6.1.2 >= )

         

        I don't know if its the hotfix I am trying to go to or what, but its very broken

      • Jonathan Read (Progress Software)

        Have your tried specifying the initial release 15.4.8600?

      • Michael Grady (Partner)

        Here is what ended up "working":

        Ran:

        Get-Package | Uninstall-Package -RemoveDependencies -Force

         

        Then from there was able to run the install command for Progress.Sitefinity.All on the empty project to get to the latest version of 15.4

         

        something in the upgrade script kept creating a dependency issue on the .unsafe library it couldn't resolve.

10 of 12