Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m giving SheepAOP a go for a new project, but i’m hitting a point where i can’t use the VS2010 debugger. The breakpoints are not recognised and it looks like the pdbs are out of sync with the weaved code.
I’ve tried it with the sample provided on the SheepAOP website, but no cigar there either.
SheepAspect produces bytecodes that are specifically intended to maintain debuggability, but one thing that I find necessary is to make sure you turn on “Just My Code” in your VS debugging options.
You could still reach your aspect code using breakpoint regardless of that option, but to make your F11(step-into) jump into your aspect, I find that “Just my code” option is required. Otherwise it will only jump thorugh your (original) code, skipping any injected aspect it may pass. (I was going to add this in the “debugging & unit-testing tips” section).
I’ve yet to investigate the root of this issue, but it seems to be a limitation within Visual Studio that seemingly just “gives up” to proceed further with the debugging whenever it runs into any instruction with no corresponding source-code. “Just my code” option prevents visual studio to get to that situation in the first place.
Let me know if that solves your problem.
(UPDATED to fix inaccurate explanation as per my comment below)