solution doesn't hit breakpoints

Question

solution doesn't hit breakpoints

g.infantino

Grasshopper

Points: 14
More actions
May 19, 2017 at 7:19 am

#336989

Hi, anywhere I put breakpoints in my solution, they're not hit, even if the command they contain is run. Run64BitRuntimeOption is correctly set to false. Any idea?

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

DamianC SSCrazy Eights Points: 8023 More actions · Answer 1

Hello

What is you package doing?
I am having a similar issue, although it works well on everything with the exception of foreach containers
I simply cannot get these working

Where it works, I set the breakpoint ad click 'Start Debugging'
foreach just steps over

I have tried practically everything
Well, except a method that works! ...

- Damian

Phil Parkin SSC Guru Points: 246960 More actions · Answer 2

Might be useful to know what version of SSDT/BIDS you are both using.

The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin

DamianC SSCrazy Eights Points: 8023 More actions · Answer 3

DamianC

SSCrazy Eights

Points: 8023

May 22, 2017 at 5:45 am

#1943528

2008 R2 for me

- Damian

Lowell SSC Guru Points: 323518 More actions · Answer 4

nevermind...you explicitly said you toggled 32 bit mode....

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

robert.gerald.taylor SSChampion Points: 13133 More actions · Answer 5

I didn't think you could step though your .Net code with a breakpoint in 2008 R2?

You might have to default to using what we called back in the day, the Prime debugger. The debugger on the Prime system was so poor, you ended up putting a bunch of PRINT statements in your code (yes, a long time ago). Worst case, you can put MessageBoxes in your script task .Net code.

Rob

JustMarie SSCertifiable Points: 7771 More actions · Answer 6

This may sound obvious but are you running the package or selecting and running a task? This makes a difference because you only get breakpoints when you run the entire package.