London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
AI OnAI Off
London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
I can agree that versioning in EPiServer is a bit tricky when it comes to get in order various moving parts in platform. You just have to get used to that :) Seems that things are getting better in >= 7.5.
Version for package in Addon store could be different from one available on NuGet feed - those are different packages.
EPiServer.Shell.dll comes from EPiServer.Framework NuGet package and there is no standalone package named `Shell`.
All versions for >= 7.0 for particular package should be available on NuGet feed.
Hello!
I am a bit confused when it comes to versioning in EPi. I have an installation which is version 7.0.586.8.
In Add-on store there is an update: EPiServer 7.1.3, which have some dependencies, e.g. Shell 2.1.97. In Visual Studio, under references, I have Episerver.Shell version 7.0.859.8. Why do they have different version number format?
Another issue is that I would like to install a specific version of a nuget package. In the NuGet package manager, I can only find the latest versions. So I tried the package manager console. But I can't find the versions I am looking for.
If I write "get-package -ListAvailable -Filter shell", the result doesn't include any Episerver.Shell package.