Is there any need to use patch:after with Unicorn configuration filesHow does the `ref` attribute work in Sitecore configuration files?Unicorn with Synthesis Solution in a Helix ImplementationNested sc.variables in Unicorn configurationUnicorn overlapping configuration issueCannot activate Unicorn.Roles.Loader.RoleLoader after unicorn 3 -> 4 upgradeHow to disable or change scheduling for backups of configuration historyWhy use Patch Files to update configuration?Setting up HelixBase with Sitecore 9.1 and unsure how to run UnicornUnable to sync page versions with UnicornCustom regex validator on display name field with helix in mind and unicorn sync
My parents are Afghan
My Sixteen Friendly Students
What are these pads?
Why did Ham the Chimp push levers?
Is there an idiom that means "revealing a secret unintentionally"?
The unknown and unexplained in science fiction
Is there an application which does HTTP PUT?
Do oversize pulley wheels increase derailleur capacity?
What dice to use in a game that revolves around triangles?
What happens when the drag force exceeds the weight of an object falling into earth?
Why doesn't increasing the temperature of something like wood or paper set them on fire?
What will Doctor Strange protect now?
Can you turn a recording upside-down?
Using mean length and mean weight to calculate mean BMI?
What are my options legally if NYC company is not paying salary?
Names of the Six Tastes
History: Per Leviticus 19:27 would the apostles have had corner locks ala Hassidim today?
Equivalent forms of the P vs. NP problem
Add elements inside Array conditionally in JavaScript
Are there vaccine ingredients which may not be disclosed ("hidden", "trade secret", or similar)?
Employee is self-centered and affects the team negatively
How do I politely tell my players to shut up about their backstory?
How do I give a darkroom course without negatives from the attendees?
Can the president of the United States be guilty of insider trading?
Is there any need to use patch:after with Unicorn configuration files
How does the `ref` attribute work in Sitecore configuration files?Unicorn with Synthesis Solution in a Helix ImplementationNested sc.variables in Unicorn configurationUnicorn overlapping configuration issueCannot activate Unicorn.Roles.Loader.RoleLoader after unicorn 3 -> 4 upgradeHow to disable or change scheduling for backups of configuration historyWhy use Patch Files to update configuration?Setting up HelixBase with Sitecore 9.1 and unsure how to run UnicornUnable to sync page versions with UnicornCustom regex validator on display name field with helix in mind and unicorn sync
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?
configuration unicorn
asked Apr 29 at 13:20
Matthew DresserMatthew Dresser
2,6811044
add a comment |
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?
configuration unicorn
asked Apr 29 at 13:20
Matthew DresserMatthew Dresser
2,6811044
add a comment |
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?
configuration unicorn
asked Apr 29 at 13:20
Matthew DresserMatthew Dresser
2,6811044
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?
configuration unicorn
configuration unicorn
asked Apr 29 at 13:20
Matthew DresserMatthew Dresser
2,6811044
asked Apr 29 at 13:20
Matthew DresserMatthew Dresser
2,6811044
asked Apr 29 at 13:20
Matthew DresserMatthew Dresser
2,6811044
asked Apr 29 at 13:20
Matthew DresserMatthew Dresser
2,6811044
asked Apr 29 at 13:20
Matthew DresserMatthew Dresser
2,6811044
2,6811044
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
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.
answered Apr 29 at 13:47
Mark Cassidy♦Mark Cassidy
18.1k53783
Cool, thanks for your answer. So in most cases, we should not needpatch: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
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "664"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f18374%2fis-there-any-need-to-use-patchafter-with-unicorn-configuration-files%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
answered Apr 29 at 13:47
Mark Cassidy♦Mark Cassidy
18.1k53783
Cool, thanks for your answer. So in most cases, we should not needpatch: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
add a comment |
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.
answered Apr 29 at 13:47
Mark Cassidy♦Mark Cassidy
18.1k53783
Cool, thanks for your answer. So in most cases, we should not needpatch: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
add a comment |
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.
answered Apr 29 at 13:47
Mark Cassidy♦Mark Cassidy
18.1k53783
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.
answered Apr 29 at 13:47
Mark Cassidy♦Mark Cassidy
18.1k53783
answered Apr 29 at 13:47
Mark Cassidy♦Mark Cassidy
18.1k53783
answered Apr 29 at 13:47
Mark Cassidy♦Mark Cassidy
18.1k53783
answered Apr 29 at 13:47
Mark Cassidy♦Mark Cassidy
18.1k53783
18.1k53783
Cool, thanks for your answer. So in most cases, we should not needpatch: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
add a comment |
Cool, thanks for your answer. So in most cases, we should not needpatch: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
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
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
1
Yes. Which in a typical Helix type setup would be something like Foundation.Serialization.
– Mark Cassidy♦
Apr 29 at 14:58
Yes. Which in a typical Helix type setup would be something like Foundation.Serialization.
– Mark Cassidy♦
Apr 29 at 14:58
add a comment |
Thanks for contributing an answer to Sitecore Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f18374%2fis-there-any-need-to-use-patchafter-with-unicorn-configuration-files%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
