November Happy Hour will be moved to Thursday December 5th.
November Happy Hour will be moved to Thursday December 5th.
We deliberately excluded components that were unchanged compared to the original release. How does this affect your solution? I'm trying to get the use case. :)
Thank you for answer. I didn't understand you. There are available all Episerver CMS components via nuget packages. Even more - there is Episerver.Mail nuget package which, if I'm right , is more Community rather than CMS component. But there isn't Community nuget pakage! What is the point? Community is built on CMS. To make Community/Relate site I should make references to both CMS assemblies and Community assemblies. And if I'm using nuget I expect that all Episerer assembly references culd be obtained via nuget. But itsn't so. Why?
You mentioned something about "unchanged compared to the original release". What does it means? Are you saying that CMS is changing but Community not, arn't you?
I think it would be nice to have Community as a nuget package aswell. Every other dependancy we have in our current project is a Nuget package. Because of that we still have to do a post-build copy of assemblies just to get Community in place.
Is there way to get Community and/or Relate+ package via nuget? There are available EPiServer.CMS.Core, EPiServer.Framework, EPiServer.Search and even EPiServer.Mail packages. But no package for EPiServer.Community?