You cannot debug assemblies that are referenced in the Script task code by using Visual Studio for Applications in SSIS (922647)
The information in this article applies to:
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Workgroup
- Microsoft SQL Server 2005 Enterprise Edition for Itanium Based Systems
- Microsoft SQL Server 2005 Enterprise X64 Edition
- SQL Server 2005 Standard Edition for Itanium-based Systems
INTRODUCTIONConsider the following scenario. You are debugging a Script task in an SSIS package in Microsoft Visual Studio for Applications. You try to step into an assembly that is referenced in the code of the Script task. In this scenario, you receive the following message:
There is no source code available for the current location. You can click Show Disassembly to view the assembly of the referenced library. However, you cannot debug the assembly. In Microsoft SQL Server 2005 Integration Services (SSIS), you cannot debug assemblies that are referenced in the Script task code by using Visual Studio for Applications. This problem occurs even if the assembly is loaded in the global assembly cache.
This article introduces a method that you can use to debug the assemblies that are referenced in an SSIS Script task by using a separate instance of Visual Studio 2005. REFERENCESFor more information, see the following Microsoft Developer Network Web site:
Modification Type: | Major | Last Reviewed: | 7/27/2006 |
---|
Keywords: | kbinfo kbtshoot kbsql2005ssis kbExpertiseAdvanced KB922647 kbAudDeveloper kbAudITPRO |
---|
|