Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Go Back   Wrox Programmer Forums > SQL Server > SQL Server 2005 > BOOK: Professional SQL Server 2005 Integration Services ISBN: 0-7645-8435-9
Password Reminder
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
BOOK: Professional SQL Server 2005 Integration Services ISBN: 0-7645-8435-9
This is the forum to discuss the Wrox book Professional SQL Server 2005 Integration Services by Brian Knight, Allan Mitchell, Darren Green, Douglas Hinson, Kathi Kellenberger, Andy Leonard, Erik Veerman, Jason Gerard, Haidong Ji, Mike Murphy; ISBN: 9780764584350
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: Professional SQL Server 2005 Integration Services ISBN: 0-7645-8435-9 section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old March 28th, 2008, 11:58 AM
Registered User
Join Date: Dec 2007
Location: , , .
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
Default Big limitation in SSIS - No unmanaged code support


I want to point out a big limitation in SSIS. One cannot reference unmanaged code. It cannot be done from Script Task, Script Components or even from Custom Components.

Why would I want to reference unmanaged code? One popular application is to generate bill documents through Word Collaboration. One reads an input file and populates insert fields in a word template (.dot).

At first, one would think merging the records from the input file with a word template could be done through a Script Task or a component. However, Word collaboration requires referencing Interop.Office.dll and Interop.Word.dll but SSIS requires assemblies to be signed meaning you cannot reference unmanaged code. In fact, you would get this error:

Error: System.IO.FileNotFoundException: Could not load file or assembly 'Interop.Word, Version=, Culture=neutral, PublicKeyToken=f764e21644c86955' or one of its dependencies.

The only solution I found is to use an Execute Process Task and wrap your unmanaged code in an exe. However, that is cumbersome. It would be nice to be able to use a Script Task, Script Component or a Custom Component.
Reply With Quote

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
a big bug on a code busteronline ASP.NET 1.0 and 1.1 Basics 0 September 15th, 2008 09:11 AM
Managed & Unmanaged Code? code_lover General .NET 0 January 4th, 2007 10:08 AM
Unmanaged to managed code blemos C# 0 December 21st, 2006 08:34 AM
Live Support Chat code surendran Classic ASP Basics 0 August 26th, 2005 11:57 PM
Using XML Schemas in C++ Unmanaged Code RFickling XML 1 June 8th, 2005 08:23 AM

All times are GMT -4. The time now is 02:25 AM.

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.