Debugging SSIS Script task - Breakpoint is enabled but it does not hit

I tried all the answers provided here with no success (using VS2015). After some more searching I found this question that is actually an answer which stated that newer C# features / syntax were causing the debugger to not fire correctly.

In their example (and also mine) using string interpolation was causing the breakpoints to not be hit.

Replacing

$"{someVariable} - {someOtherVariable}"

with

string.Format("{0} - {1}", someVariable, someOtherVariable);

did the trick for me.

EDIT

It appears this issue has now been fixed with SQL Server Integration Services Projects, but you need to be running VS2019 to download it.

Update: Guys, I againg lost any ability to set breakpoints (a request to MS)
My previous fixes are below.
Now I'm using logging and tracing instead of debugging.

C# new features (after C# 4.0) are blamed for killing debugging of the SSIS Script Task.

To return the breakpoint capability I do the following.

1. Remove C# new features
2. Run my Script Task once, successfully. I.e. without a crash.
3. Reopen the Vsta Project from my Script Task and put breakpoints there.

At the end, you have to see a red circle on your Script Task.
(Tested in VS 2017.)

Note. I have to mention that debugging works even if your use "Execute Task" only, not "Execute Package"!

Remove C# new features

To remove the C# new features, I can advise you two ways.

First, restrict Vsta Project properties to C# 4.0 (migrated packages may not support this).

1. Dobule click your "Script Task" to open "Script Task Editor".
2. Click "Edit Script..." button to open Visual Studio.
3. In "Solution Explorer" select the project and click the F4 key on your keyboard.
4. In opened "Properties" window in "C# Language Level" choise "C# 4.0"
5. Build your project and fix compilation errors.

Secondly, Vsta Projects in old/migrated packages may not show the above "C# Language Level" property.
So you can put your code in a fake project in Visual Studio 2010 and compile it there.

Run it once successfully

After you fix your C#, you have to run your Script Task once successfully.
You may want to put the return statement at the beginning of the Main() method to prevent any real execution.
Sorry, this doesn't always work and I don't realise why but you definitely need to fix your C# in the first place.
At least you will get a working Script Task and can debug it in an old fashioned way (logs by Dts.Events..., exceptions, etc.)

TL;DR

It looks like I even got severe cases when C# new features forced Script Tasks to fail silently with a success completion status.

As an example, add the following to your Script task.

string Bug { get; } // Only getter properties.
//...
var str = $"Now is {DateTime.Now}"; // String Interpolation in C#
//...
var dummy = val?.ToUpper(); // ?. and ?[] null-conditional Operators

And workarounds for this non-complete list:

string Bug { get; set; }
//...
var str = string.Format("Now is {0}", DateTime.Now);
// etc.

What I also do, I build my C# code in Visual Studio 2010. It simply doesn't compile the new .NET features and do not allows .NET Framework versions above 4.0. So far, so good.

Of course, other answers from this SO-question didn't help me.

In my case, none of these solutions worked. I finally got to know that the Resharper was culprit. After uninstalling it, it started working like charm.

In my case, I had to get rid of all features from C# 6: string interpolation, null conditional operators (?., ?(), ?[]) and expression-bodied members (=>) (there might be more in your case). You can check them all here. Of course, the same applies to C# 7 features.

The 32/64 bit changes from other answers didn't help, so I rolled back those and the debugging kept working just fine.

Use System.Diagnostics.Debugger class to add breakpoint programmatically:

System.Diagnostics.Debugger.Launch();
System.Diagnostics.Debugger.Break();

You can check if the debugger is attached or not:

    if (System.Diagnostics.Debugger.IsAttached)
        System.Diagnostics.Debugger.Break();

Follow these step:

1. Keep your project or solution opened.
2. Run your app to hit breakpoint.
3. Select your project in Just-In-Time Debugger.

I inherited an SSIS package where unfortunately the above answers didn't help.

In the end I found the script task's build properties for debug mode had had the optimize code ticked. Make sure this isn't ticked because for me visual studio would fire up for script debugging and close shortly after without breaking at all.

Pretty obscure but worth a mention.

We hit the same problem recently. For us the solution was to ensure that the script task project was marked to run as with the platform target set to x86.

1. Edit the script task
2. Click on the project and select properties
3. Select to set the platform target to x86

I spent whole day on this and NONE of the solutions mentioned here worked for me.

In my case, the existing project was targeted to SQL Server 2016 which defaults ScriptLanguage Microsoft Visual c# 2015. This doesn't allow debugging in VS 2019. I have to target project to SQL Server 2019 to make debugging work. Of course, I am not going to checkin version change. It's only to debug script. Once script is working, I am going to revert target version to SQL server 2016.

Hope this saves time for someone.

In addition to Jeff's suggestion, also change the Platform Target to "x86" (In the script's properties' Build tab. This FINALLY got me debugging again on a 64-bit system.

Microsoft released an update v3.2 of SQL Server Integration Services Projects where it resolves the issue with Roslyn and other C# language features introduced after .Net 4.5. C# features.
Bad news - this fix is for Visual Studio 2019 only, you have to upgrade your VS to use it.

I had the same problem as you @PAS. Using VS 2019 and Target server version 2016. Just found out that if upgrading SSIS in Visual Studio (going into Extensions->Manage Extensions) to latest version (which now is 3.15) debugging is now working.

My breakpoints refused to hit no matter what I did. I ended up debugging and fixing the issues just using exception throws. Once I had fixed the issues I was having, the breakpoints started hitting!

So my breakpoints would only hit once the code did not experience any runtime issues... which is bizarre.

In my experience, it doesn't matter:

• if Run64BitRuntime is true or false
• if you build the 32 or 64 bits version of your package

But there is something very important, not mentioned in any other answer: you must run the whole package. If you run a Task or a Container the breakpoint will be ignored.

I'm using Visual Studio 2013, on a 64 bits machine.

I only had one Script component were no breakpoints were hit (I was doing some CRM stuff without needing source/target). I trid to add a Source componenet with a simple fetchXML (even if I didn't needed it). Then it worked! :-)

I found out that by copying a Script Component task, the VSTA project as a whole is copied as well. This is what you would expect, but what I did not expect is with that, the assembly name for example is also copied. Running then Execute Task works fine, but running the whole package actually only runs the first script that was copied and resulted in exceptions being thrown before ever hitting the row processing function. That was also the reason for me that breakpoints were not being hit.

Hope my experience can help.

Here is my scenario. I have VS2022 with SSDT. My SSIS project work properly and able to hit Breakpoint of Script task. However, it failed to start after upgraded to VS2022 V17.13.2. I have tried all solutions mentioned above, but still not able to start the debugging in VS2002.

Finally, I solve it by uninstall the SSIS Extension and reinstall it again. The breakpoint in Script task can be hit again in debugging mode. Here is the steps:

1. Start VS2022 and click "Continue without code"
2. Click "Extensions" and "Manage Extensions"
3. Find "SQL Server Integration Services Project 2022" in "Installed", and then click "Uninstall"
4. Restart computer
5. Start VS2022 and go to "Manage Extensions" again
6. Search "SQL Server Integration Services Project 2022" in "Browse"
7. Click "Install", download latest SSDT and install again.

Hope this solution can help. Good luck.