Copied to clipboard

Flag this post as spam?

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

  • Anthony 26 posts 145 karma points
    Oct 11, 2022 @ 10:27

    Installing packages: v9+ only possible with Nuget

    Umbraco package installation has changed in v9+ to a Nuget only mechanism.

    I'm wondering what the motivation was behind this? I assume it simplifies things and offloads much of the heavy lifting and support away from the Umbraco ecosystem and puts in the .NET space. I get that.

    Although packages were sometimes "twitchy", I previously used them on occasion to quickly move content\document types\data types etc. around [between Umbraco installations].

    I know uSync, Umbraco Deploy or a database copy, will do these things too, but they're not always convenient\available\installed\quick. Is there another way?

    It also seems a bit odd that packages can still be created when they can't be imported (am I wrong?!).

    It seems like we may have lost something here....

  • Paul Daly ( 40 posts 393 karma points c-trib
    Oct 11, 2022 @ 10:57
    Paul Daly (

    Hi Anthony

    You can find out all the reasons for the move to NuGet only packages here, in this blog post:


    Paul from uSkinned

  • Anthony 26 posts 145 karma points
    Oct 11, 2022 @ 12:19

    Cheers Paul. That satisfies both my curiosity and helps resolve the issue I was trying to overcome :)

    The "other way" I was looking for was to create a NuGet package based on a package (package.xml) created from Umbraco 10 and use that to generate an Umbraco database migration to move my content from one Umbraco instance to another (ref:

    Not exactly quick or simple, but gets the job done.

    Many thanks.

  • Søren Kottal 693 posts 4405 karma points MVP 5x c-trib
    Oct 11, 2022 @ 12:22
    Søren Kottal

    Hi Anthony

    Maybe this package can be helpful?

Please Sign in or register to post replies

Write your reply to: