1

I'm working in a Helix solution and have noticed things like:

<configuration name="Feature.MyModuleName"
               dependencies="Foundation.SomethingElse" 
               patch:after="configuration[@name='Foundation.Core']">

To me, the dependencies attribute seems like all you should need.

Is it really necessary patch:after as well as the dependencies attribute?

3

Yes. At least potentially.

patch:after happens when Sitecore.Configuration.Factory reads and parses and constructs the object graph that the configuration represents. So at Initialize time of the application. There could be Foundation level configuration entries (like default serializer and so on) that need to be set up, before your Feature level configuration is read and parsed.

The dependencies attribute affects Unicorn sync order at runtime. So much much later in process/lifecycle of your application.

  • Cool, thanks for your answer. So in most cases, we should not need patch:before; only when there is something which changes the behaviour of serialization/unicorn. – Matthew Dresser Apr 29 at 14:49
  • 1
    Yes. Which in a typical Helix type setup would be something like Foundation.Serialization. – Mark Cassidy Apr 29 at 14:58

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.