Debuging SSIS Script Component In Visual Studio

Question

Post reply

Debuging SSIS Script Component In Visual Studio

neil.walker

SSC Enthusiast

Points: 116
More actions
August 31, 2016 at 7:29 pm

#329762

Hi,
My development environment has recently been migrated from one cloud environment (Microsoft SQL Server 2014 - 12.0.4213.0 (X64) ) to another (Microsoft SQL Server 2016 (RTM) - 13.0.1601.5 (X64)).
In the old environment I could set breakpoints and step through the code (C#) in the script component. In the new environment the breakpoints are disregarded. Leaving me with no way of stepping through the code.
So far I've set the Debugging setting "Run64BitRuntime" to "False", recompiled the script, and restarted Visual Studio. In the current package there is only a "Data Flow Task" in the "Control Flow".
Any suggestions? I've just started developing solutions using the MS Dynamics CRM SDK, and stepping through the code is of great benefit.
Thanks,
Neil.

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

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

Phil Parkin SSC Guru Points: 246988 More actions · Answer 1

Which version of SSDT are you using?

The absence of evidence is not evidence of absence.
Martin Rees

You can lead a horse to water, but a pencil must be lead.
Stan Laurel

neil.walker SSC Enthusiast Points: 116 More actions · Answer 2

According to VS its SQL Server Data Tools 14.0.60629.0 for the new environment. For the old environment it's

SQL Server Data Tools 12.0.50730.0.

Phil Parkin SSC Guru Points: 246988 More actions · Answer 3

Ok, I'm away from my PC right now, so can't check details.

Have you tried creating a brand new solution/project and adding a new package to it? Just to rule out any legacy/upgrade issues.

The absence of evidence is not evidence of absence.
Martin Rees

You can lead a horse to water, but a pencil must be lead.
Stan Laurel

neil.walker SSC Enthusiast Points: 116 More actions · Answer 4

I have created packages from scratch, as well as migrating solutions from the old environment.

neil.walker SSC Enthusiast Points: 116 More actions · Answer 5

This is really weird. Out of frustration I moved a SSIS package into the old development environment and did my debugging. I then moved the package back into the new environment, but I forgot to remove my breakpoints. I then executed the package and it stops at the breakpoints. I cannot work this out.

For the past three weeks I have not been able to step through my script components. Being a small company I'm sure nothing else has changed, otherwise I would have heard about it.