Sign in Register
Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Heather Floyd 531 posts 787 karma points MVP 2x c-trib
    Sep 25, 2019 @ 20:58
    Heather Floyd
    0

    Nuget update to "Umbraco Cms Core" v 7.15.3 messes with dependent package versions?

    I have noticed this behavior on two separate Umbraco Cloud sites. Both have been updated to version 7.15.3 by the Cloud automated mechanism. Both have the same Visual Studio structure - the .Web project and the .Core class project.

    After pulling the upgrade via GIT, it makes sense to use NuGet to update the related .Core project to the same Umbraco version...

    However, when I use the "Consolidate" tab on the VS NuGet interface, and update the .Core project to use Umbraco Cms Core v7.15.3... Suddenly I have 22 additional NuGet packages which need to be "consolidated". These are all Umbraco dependencies. The "updated" version on the .Core project is a few versions higher than in the .Web project, which is very strange.

    I'm not sure if the Umbraco Cloud update just failed to update the package references for the .Web project... or there is something fishy with the Nuget package for Umbraco.Cms.Core... 

    | Package                         | Version in .Web | Version in .Core |
|---------------------------------|-----------------|------------------|
| Microsoft.AspNet.Identity.Core  | 2.2.1           | 2.2.2            |
| ImageProcessor.Web              | 4.8.7           | 4.10.0.100       |
| Microsoft.AspNet.Identity.Owin  | 2.2.1           | 2.2.2            |
| Examine                         | 0.1.89          | 0.1.90           |
| Microsoft.AspNet.Mvc            | 5.2.3           | 5.2.7            |
| ImageProcessor                  | 2.5.6           | 2.7.0.100        |
| Microsoft.AspNet.Razor          | 3.2.3           | 3.2.7            |
| Microsoft.AspNet.WebApi         | 5.2.3           | 5.2.7            |
| HtmlAgilityPack                 | 1.4.9.5         | 1.8.8            |
| Microsoft.AspNet.WebApi.Client  | 5.2.3           | 5.2.7            |
| Microsoft.AspNet.SignalR.Core   | 2.2.1           | 2.4.1            |
| Microsoft.AspNet.WebApi.Core    | 5.2.3           | 5.2.7            |
| Microsoft.Owin                  | 3.1.0           | 4.0.1            |
| Microsoft.AspNet.WebApi.WebHost | 5.2.3           | 5.2.7            |
| Microsoft.AspNet.WebPages       | 3.2.3           | 3.2.7            |
| Microsoft.Owin.Security         | 3.1.0           | 4.0.1            |
| Microsoft.Owin.Host.SystemWeb   | 3.1.0           | 4.0.1            |
| Microsoft.Owin.Security.OAuth   | 3.1.0           | 4.0.1            |
| System.ValueTuple               | 4.4.0           | 4.5.0            |
| Microsoft.Owin.Security.Cookies | 3.1.0           | 4.0.1            |
| Newtonsoft.Json                 | 10.0.2          | 12.0.2           |
| System.Threading.Tasks.Dataflow | 10.0.2          | 12.0.2           |

    Has anyone else seen this in their projects?

    Copy Link
  • Heather Floyd 531 posts 787 karma points MVP 2x c-trib
    Sep 25, 2019 @ 21:41
    Heather Floyd
    0

    Okay, so I am thinking that the issue is that the Umbraco Cloud update didn't update the references to the dependent packages, because if I use the Package Manager Console in VS, and with the .Web project selected and run:

    PM > Update-Package UmbracoCms.Core -Version 7.15.3

    The .Web dependencies get updated as well.

    This does now show a bunch of changed files in the /bin/ directory for the .Web project when I look at GIT, which seems to indicate that those files weren't actually updated via Umbraco Cloud's update procedure.

    I'm not sure what to make of this, exactly, but my local version of the site seems to run just fine - no issues on the front-end or the back-office as far as I can tell...

    Copy Link
  • Heather Floyd 531 posts 787 karma points MVP 2x c-trib
    Nov 05, 2019 @ 16:38
    Heather Floyd
    100

    FYI: Received response from Umbraco Cloud Support:

    Hi Heather,

    I've been able to reproduce the issue you was experiencing. It's not that the packages aren't updated though from what I can see. It's that the packages.config is not updated correctly for all packages that were involved in that update.

    The Umbraco packages are added correctly but when you check the other packages you will see that they are still displaying the old version. You can see this by checking the details of the dll files in the bin folder. Here's an example of one of them. I found an issue on the Cloud tracker where a similar problem is reported - https://github.com/umbraco/Umbraco.Cloud.Issues/issues/67

    It was believed to have been solved but I'll ask Sebastiaan about it and either reopen or create a new issue on it. So the bottom line is that the project is upgraded correctly but the information about what was updated is not.

    All the best / Mahmoud

    Copy Link

  • This forum is in read-only mode while we transition to the new forum.

    You can continue this topic on the new forum by tapping the "Continue discussion" link below.

Please Sign in or register to post replies