In .NET Core, packages are declared inside of the csproj file, as "PackageReference". The overall idea of a packages.config does not exist in dotnet core.
.NET Core will always use the Package Reference, so we can say goodbye to the package.config!
@Corné I realise my question had some ambiguity in {package}.config- I'm referring to custom Umbraco package configuration.
@Søren, very useful video. I was looking for a pattern that could be modified & persisted at runtime to allow users to modify settings via the CMS. However, I think for the package I'm migrating Config builders will work just fine.
I would still be interested to hear how other packages are handling custom config in the CMS.
Where to store Umbraco 9 package config
In the past, packages have often stored custom configuration in config/{package}.config.
Are there any recommendations on where config should be stored in v9?
Hi Anthony
In .NET Core, packages are declared inside of the csproj file, as "PackageReference". The overall idea of a packages.config does not exist in dotnet core.
.NET Core will always use the Package Reference, so we can say goodbye to the package.config!
Hi Anthony
Check out this video about configuration & options in packages where Warren Buckley explores methods for handling package specific config.
Thanks both.
@Corné I realise my question had some ambiguity in {package}.config- I'm referring to custom Umbraco package configuration.
@Søren, very useful video. I was looking for a pattern that could be modified & persisted at runtime to allow users to modify settings via the CMS. However, I think for the package I'm migrating Config builders will work just fine.
I would still be interested to hear how other packages are handling custom config in the CMS.
For others new to the topic, there's a great introduction to config in Umbraco 9 referenced in Warrens video: https://24days.in/umbraco-cms/2020/umbraco-dotnet-core-config/
is working on a reply...
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.