volume_up

A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More. 

volume_up

A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More. 
AI OnAI Offsmart_toy

Package handling

Mikael Hansson
Mikael Hansson
Vote:
expand_less 0 expand_more

What's the preferred way to handle packages in CMS 12?

At the moment I only have EPiServer.CMS referenced and all dependencies are handled automatically. That seems to keep the dependencies at the lowest possible version though.

Any suggestions about this?

/Mikael

#286836
Sep 08, 2022 13:07
Quan Mai
Quan Mai
Vote:
expand_less 0 expand_more

That is the default behavior of nuget NuGet Package Dependency Resolution | Microsoft Docs (lowest compatible version) 

In previous version of VIsual Studio I think you have the option to change that, however it is no longer available in 2022 as I checked it 

#286837
Sep 08, 2022 13:28
Johan Book
Johan Book
Vote:
expand_less 0 expand_more

Magnus Rahl has written an in-depth article about how nuget dependencies are resolved with the new model.

We ended up referencing a handful of packages in order to get to the latest versions.

#287423
Sep 15, 2022 6:43
Tomas Hensrud Gulla
Tomas Hensrud Gulla
Vote:
expand_less 0 expand_more

I think I've often ended up referenceing more than a handful of packages, but an Optimizely engineer once recommended me directly installing the following packages.

  • EPiServer.CMS
  • EPiServer.Hosting
  • EPiServer.CMS.AspNetCore.HtmlHelpers
#287440
Sep 15, 2022 12:30
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.