Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
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....
You can find out all the reasons for the move to NuGet only packages here, in this blog post: https://umbraco.com/blog/packages-in-umbraco-9-via-nuget/
Paul from uSkinned
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: https://our.umbraco.com/Documentation/Extending/Packages/Creating-a-Package/).
Not exactly quick or simple, but gets the job done.
Maybe this package can be helpful? https://github.com/hfloyd/Dragonfly.Umbraco10.SchemaImporter
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted