SSIS Script Editor throws an exception

visual-studio-2010 ssis bids vsta
Raymond Saltrelli picture Raymond Saltrelli · May 3, 2012 · Viewed 20.6k times · Source

I have SQL Server 2012, SSIS, SSDT and Visual Studio 2010. I can create a new SSIS package and add a Script Task, but if I attempt to open the Script Editor for that Script Task I get the following error:

TITLE: Microsoft Visual Studio
------------------------------

Cannot show Visual Studio 2010 Tools for Applications editor.

------------------------------
ADDITIONAL INFORMATION:

Could not load file or assembly 'Microsoft.VisualStudio.Tools.Applications.Core, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. (mscorlib)

------------------------------
BUTTONS:

OK
------------------------------

From my own investigation into this error, I found that Visual Studio Tools for Applications appears to be a part of MS Office 2007 and higher. This seemed like an odd dependency for to have, but I installed MS Office 2010 just for grins. It didn't change anything. What else should I try?

Answer

Anoop Verma picture Anoop Verma · Jan 31, 2013

You will also get this error, if you are trying to debug a script task in VS 2010 and Run64BitRuntime is set to true. In order to debug, set it to false.

Related questions

SSIS Excel Connection Manager failed to Connect to the Source

I have a server that is capable of creating and running an Excel Import task using the Import Wizard. I am trying to automate that process by using a visual Studio 2010 Integration Services package, that I am developing on that …

Read More
Is it possible to deploy SSIS 2012 package on SQL Server 2008

I have a package that is developed in SSIS 2012 using Visual Studio 2010. Is it possible to deploy/attach this package on SQL Server 2008 If it is possible, does the licence of the sql server matter

Read More
SSIS package fails in sql server agent, but not in visual studio. ODBC Connection

I have an SSIS package that runs fine in visual studio 2010, but as a job it sql server it fails when connecting to an ODBC database. The project encrypts sensitive data with a password. This is because the proxy server …

Read More