I'm having a strange problem with a package. If I ...
# package-developmenth
huwred
02/28/2023, 9:03 AMI'm having a strange problem with a package. If I install it from my local nuget repositry everything works fine and the package installs in umbraco, however if I upload the package to nuget and install the package from there, when I run umbraco I get the following error
Copy code
BootFailedException: Boot failed: Umbraco cannot run. See Umbraco's log file for more details.
-> Umbraco.Cms.Core.Exceptions.BootFailedException: Value cannot be null. (Parameter 'packageXmlFile')
-> System.ArgumentNullException: Value cannot be null. (Parameter 'packageXmlFile')
at Umbraco.Cms.Infrastructure.Packaging.PackageInstallation.ReadPackage(XDocument packageXmlFile)s
Sebastiaan
02/28/2023, 9:13 AMI'm assuming you're embedding a package.zip with doctype definitions etc.?
Something is wrong with that 😅
Sebastiaan
02/28/2023, 9:15 AM@CodeSharePaul does it like this:
Embed the zip file: https://github.com/prjseal/Clean-Starter-Kit-for-Umbraco-v9/blob/main/Clean/Clean.csproj#L42
Use it in the migration: https://github.com/prjseal/Clean-Starter-Kit-for-Umbraco-v9/blob/main/Clean/Migrations/ImportPackageXmlMigration.cs#L35
h
huwred
02/28/2023, 9:19 AMI'm embedding a package.xml not zip, but yes the code looks like that, and installs perfectly from a local repo just not when installed from nuget, (same nuget package)
s
Sebastiaan
02/28/2023, 9:22 AMAny chance you can send me the nupkg file here?
Sebastiaan
02/28/2023, 9:23 AMInstalling in v10 or 11?
h
huwred
02/28/2023, 9:28 AMGrrrr, it was the nuget cache! I cleared it out and reinstalled, now all working 😄
This is the package, but all good now I'v cleaned out my nuget cache 😢
https://github.com/users/huwred/packages/nuget/package/Umbraco.Community.FullCalendar.Block
s
Sebastiaan
02/28/2023, 9:34 AMI was going to say that.. lol
Sebastiaan
02/28/2023, 9:39 AMSo the one pro-tip I have for you: never, ever, set up local NuGet source ⚠️
Those will be cached, and then when you try to fetch the package that you've changed 10 times since the first build locally from remote NuGet, you get the version that was locally cached.
Work around this by using NuGet commands to point to a package source while developing:
dotnet add package Cultiv.Hangfire --source D:\Dev\Cultiv.Hangfire\Release --prerelease--sourcedotnet build --configuration Release /p:Version=2.2.2-rc001rc002rc003rc002