Is there a way to debug an initialize pipeline processor
I've used JeffDarchuk's EPExpressTab in an exercise to show some custom data. I've used the quick & dirty part.
It worked to certain extent, since I ported the code to my solution. I have my custom tab, but the other tabs vanished.
Is there a way to debug the Initialize pipeline which is defined in the processor type ?
<processor type="EPExpressTab.Pipelines.Initialize.Initialize, EPExpressTab" ></processor>
pipelines
edited Dec 6 '18 at 18:36
jammykam
11.1k11755
asked Dec 6 '18 at 16:56
BakudanBakudan
1276
add a comment |
I've used JeffDarchuk's EPExpressTab in an exercise to show some custom data. I've used the quick & dirty part.
It worked to certain extent, since I ported the code to my solution. I have my custom tab, but the other tabs vanished.
Is there a way to debug the Initialize pipeline which is defined in the processor type ?
<processor type="EPExpressTab.Pipelines.Initialize.Initialize, EPExpressTab" ></processor>
pipelines
edited Dec 6 '18 at 18:36
jammykam
11.1k11755
asked Dec 6 '18 at 16:56
BakudanBakudan
1276
add a comment |
I've used JeffDarchuk's EPExpressTab in an exercise to show some custom data. I've used the quick & dirty part.
It worked to certain extent, since I ported the code to my solution. I have my custom tab, but the other tabs vanished.
Is there a way to debug the Initialize pipeline which is defined in the processor type ?
<processor type="EPExpressTab.Pipelines.Initialize.Initialize, EPExpressTab" ></processor>
pipelines
edited Dec 6 '18 at 18:36
jammykam
11.1k11755
asked Dec 6 '18 at 16:56
BakudanBakudan
1276
I've used JeffDarchuk's EPExpressTab in an exercise to show some custom data. I've used the quick & dirty part.
It worked to certain extent, since I ported the code to my solution. I have my custom tab, but the other tabs vanished.
Is there a way to debug the Initialize pipeline which is defined in the processor type ?
<processor type="EPExpressTab.Pipelines.Initialize.Initialize, EPExpressTab" ></processor>
pipelines
pipelines
edited Dec 6 '18 at 18:36
jammykam
11.1k11755
asked Dec 6 '18 at 16:56
BakudanBakudan
1276
edited Dec 6 '18 at 18:36
jammykam
11.1k11755
asked Dec 6 '18 at 16:56
BakudanBakudan
1276
edited Dec 6 '18 at 18:36
jammykam
11.1k11755
edited Dec 6 '18 at 18:36
jammykam
11.1k11755
edited Dec 6 '18 at 18:36
jammykam
11.1k11755
11.1k11755
asked Dec 6 '18 at 16:56
BakudanBakudan
1276
asked Dec 6 '18 at 16:56
BakudanBakudan
1276
asked Dec 6 '18 at 16:56
BakudanBakudan
1276
1276
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Yes, you can debug processors in the <initialize> pipeline the same as any other pipeline in Sitecore: set your breakpoints and attach to the w3p process from Visual Studio.
The issue is that the <initialize> pipeline only runs once when the application starts up, but normally you are attaching to debug the process after that code has already run.
The trick to debug the initialize processors is to:
- Set your breakpoints in Visual Studio
- Attach to the w3p process to debug the code as normal
- Make a small edit to the deployed
web.configfile in the deployed inetpub folder. You can just add a space and save the file, or recycle the Recycle the Application Pool for your website instance in IIS - Make a request to website whilst the debugger is still attached in Visual Studio
This should cause the initialization code to fire again and the processors to run, allowing you to debug and hit your breakpoints.
answered Dec 6 '18 at 17:26
jammykamjammykam
11.1k11755
add a comment |
Yes it is possible to debug processors even if they are Sitecore out-of-the-box ones. Here two articles(link 1, link 2) with step-by-step actions you can take to achieve that.
But in a nutshell, if you are using DotPeaks you can:
a) start a SymbolServer and select which assemblies you want to load. This will create pdbs of those assemblies for you so you can attach the debugger to then
b) Update Visual Studio in Tools - Options - Debugging - Symbols and add the Symbol server that DotPeak creates for you. By default it´s "localhost:33417"
c) Still in the Dubbuging section - General, uncheck "Enable Just My Code"
d) At this point you are pretty much set. If you open the processor using Assembly Explorer and putting a breakpoint in it, you should be able to see it.
Hope this helps
answered Dec 6 '18 at 17:21
DiegoDiego
4,1211941
I would like to see more detail in this answer. I realize you're helping by providing some links, but that does equate to more of a link only answer. Perhaps synthesize some of the content from those links into part of the answer and help to build more of a step by step?
– Pete Navarra
Dec 6 '18 at 17:38
updated answer with more info
– Diego
Dec 6 '18 at 17:57
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%2f15418%2fis-there-a-way-to-debug-an-initialize-pipeline-processor%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Yes, you can debug processors in the <initialize> pipeline the same as any other pipeline in Sitecore: set your breakpoints and attach to the w3p process from Visual Studio.
The issue is that the <initialize> pipeline only runs once when the application starts up, but normally you are attaching to debug the process after that code has already run.
The trick to debug the initialize processors is to:
- Set your breakpoints in Visual Studio
- Attach to the w3p process to debug the code as normal
- Make a small edit to the deployed
web.configfile in the deployed inetpub folder. You can just add a space and save the file, or recycle the Recycle the Application Pool for your website instance in IIS - Make a request to website whilst the debugger is still attached in Visual Studio
This should cause the initialization code to fire again and the processors to run, allowing you to debug and hit your breakpoints.
answered Dec 6 '18 at 17:26
jammykamjammykam
11.1k11755
add a comment |
Yes, you can debug processors in the <initialize> pipeline the same as any other pipeline in Sitecore: set your breakpoints and attach to the w3p process from Visual Studio.
The issue is that the <initialize> pipeline only runs once when the application starts up, but normally you are attaching to debug the process after that code has already run.
The trick to debug the initialize processors is to:
- Set your breakpoints in Visual Studio
- Attach to the w3p process to debug the code as normal
- Make a small edit to the deployed
web.configfile in the deployed inetpub folder. You can just add a space and save the file, or recycle the Recycle the Application Pool for your website instance in IIS - Make a request to website whilst the debugger is still attached in Visual Studio
This should cause the initialization code to fire again and the processors to run, allowing you to debug and hit your breakpoints.
answered Dec 6 '18 at 17:26
jammykamjammykam
11.1k11755
add a comment |
Yes, you can debug processors in the <initialize> pipeline the same as any other pipeline in Sitecore: set your breakpoints and attach to the w3p process from Visual Studio.
The issue is that the <initialize> pipeline only runs once when the application starts up, but normally you are attaching to debug the process after that code has already run.
The trick to debug the initialize processors is to:
- Set your breakpoints in Visual Studio
- Attach to the w3p process to debug the code as normal
- Make a small edit to the deployed
web.configfile in the deployed inetpub folder. You can just add a space and save the file, or recycle the Recycle the Application Pool for your website instance in IIS - Make a request to website whilst the debugger is still attached in Visual Studio
This should cause the initialization code to fire again and the processors to run, allowing you to debug and hit your breakpoints.
answered Dec 6 '18 at 17:26
jammykamjammykam
11.1k11755
Yes, you can debug processors in the <initialize> pipeline the same as any other pipeline in Sitecore: set your breakpoints and attach to the w3p process from Visual Studio.
The issue is that the <initialize> pipeline only runs once when the application starts up, but normally you are attaching to debug the process after that code has already run.
The trick to debug the initialize processors is to:
- Set your breakpoints in Visual Studio
- Attach to the w3p process to debug the code as normal
- Make a small edit to the deployed
web.configfile in the deployed inetpub folder. You can just add a space and save the file, or recycle the Recycle the Application Pool for your website instance in IIS - Make a request to website whilst the debugger is still attached in Visual Studio
This should cause the initialization code to fire again and the processors to run, allowing you to debug and hit your breakpoints.
answered Dec 6 '18 at 17:26
jammykamjammykam
11.1k11755
answered Dec 6 '18 at 17:26
jammykamjammykam
11.1k11755
answered Dec 6 '18 at 17:26
jammykamjammykam
11.1k11755
answered Dec 6 '18 at 17:26
jammykamjammykam
11.1k11755
11.1k11755
add a comment |
add a comment |
Yes it is possible to debug processors even if they are Sitecore out-of-the-box ones. Here two articles(link 1, link 2) with step-by-step actions you can take to achieve that.
But in a nutshell, if you are using DotPeaks you can:
a) start a SymbolServer and select which assemblies you want to load. This will create pdbs of those assemblies for you so you can attach the debugger to then
b) Update Visual Studio in Tools - Options - Debugging - Symbols and add the Symbol server that DotPeak creates for you. By default it´s "localhost:33417"
c) Still in the Dubbuging section - General, uncheck "Enable Just My Code"
d) At this point you are pretty much set. If you open the processor using Assembly Explorer and putting a breakpoint in it, you should be able to see it.
Hope this helps
answered Dec 6 '18 at 17:21
DiegoDiego
4,1211941
I would like to see more detail in this answer. I realize you're helping by providing some links, but that does equate to more of a link only answer. Perhaps synthesize some of the content from those links into part of the answer and help to build more of a step by step?
– Pete Navarra
Dec 6 '18 at 17:38
updated answer with more info
– Diego
Dec 6 '18 at 17:57
add a comment |
Yes it is possible to debug processors even if they are Sitecore out-of-the-box ones. Here two articles(link 1, link 2) with step-by-step actions you can take to achieve that.
But in a nutshell, if you are using DotPeaks you can:
a) start a SymbolServer and select which assemblies you want to load. This will create pdbs of those assemblies for you so you can attach the debugger to then
b) Update Visual Studio in Tools - Options - Debugging - Symbols and add the Symbol server that DotPeak creates for you. By default it´s "localhost:33417"
c) Still in the Dubbuging section - General, uncheck "Enable Just My Code"
d) At this point you are pretty much set. If you open the processor using Assembly Explorer and putting a breakpoint in it, you should be able to see it.
Hope this helps
answered Dec 6 '18 at 17:21
DiegoDiego
4,1211941
I would like to see more detail in this answer. I realize you're helping by providing some links, but that does equate to more of a link only answer. Perhaps synthesize some of the content from those links into part of the answer and help to build more of a step by step?
– Pete Navarra
Dec 6 '18 at 17:38
updated answer with more info
– Diego
Dec 6 '18 at 17:57
add a comment |
Yes it is possible to debug processors even if they are Sitecore out-of-the-box ones. Here two articles(link 1, link 2) with step-by-step actions you can take to achieve that.
But in a nutshell, if you are using DotPeaks you can:
a) start a SymbolServer and select which assemblies you want to load. This will create pdbs of those assemblies for you so you can attach the debugger to then
b) Update Visual Studio in Tools - Options - Debugging - Symbols and add the Symbol server that DotPeak creates for you. By default it´s "localhost:33417"
c) Still in the Dubbuging section - General, uncheck "Enable Just My Code"
d) At this point you are pretty much set. If you open the processor using Assembly Explorer and putting a breakpoint in it, you should be able to see it.
Hope this helps
answered Dec 6 '18 at 17:21
DiegoDiego
4,1211941
Yes it is possible to debug processors even if they are Sitecore out-of-the-box ones. Here two articles(link 1, link 2) with step-by-step actions you can take to achieve that.
But in a nutshell, if you are using DotPeaks you can:
a) start a SymbolServer and select which assemblies you want to load. This will create pdbs of those assemblies for you so you can attach the debugger to then
b) Update Visual Studio in Tools - Options - Debugging - Symbols and add the Symbol server that DotPeak creates for you. By default it´s "localhost:33417"
c) Still in the Dubbuging section - General, uncheck "Enable Just My Code"
d) At this point you are pretty much set. If you open the processor using Assembly Explorer and putting a breakpoint in it, you should be able to see it.
Hope this helps
answered Dec 6 '18 at 17:21
DiegoDiego
4,1211941
edited Dec 6 '18 at 17:57
answered Dec 6 '18 at 17:21
DiegoDiego
4,1211941
answered Dec 6 '18 at 17:21
DiegoDiego
4,1211941
answered Dec 6 '18 at 17:21
DiegoDiego
4,1211941
4,1211941
I would like to see more detail in this answer. I realize you're helping by providing some links, but that does equate to more of a link only answer. Perhaps synthesize some of the content from those links into part of the answer and help to build more of a step by step?
– Pete Navarra
Dec 6 '18 at 17:38
updated answer with more info
– Diego
Dec 6 '18 at 17:57
add a comment |
I would like to see more detail in this answer. I realize you're helping by providing some links, but that does equate to more of a link only answer. Perhaps synthesize some of the content from those links into part of the answer and help to build more of a step by step?
– Pete Navarra
Dec 6 '18 at 17:38
updated answer with more info
– Diego
Dec 6 '18 at 17:57
I would like to see more detail in this answer. I realize you're helping by providing some links, but that does equate to more of a link only answer. Perhaps synthesize some of the content from those links into part of the answer and help to build more of a step by step?
– Pete Navarra
Dec 6 '18 at 17:38
I would like to see more detail in this answer. I realize you're helping by providing some links, but that does equate to more of a link only answer. Perhaps synthesize some of the content from those links into part of the answer and help to build more of a step by step?
– Pete Navarra
Dec 6 '18 at 17:38
updated answer with more info
– Diego
Dec 6 '18 at 17:57
updated answer with more info
– Diego
Dec 6 '18 at 17:57
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%2f15418%2fis-there-a-way-to-debug-an-initialize-pipeline-processor%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
