1

Closed

Converting the project for SQL Server 2005

description

I'm trying to convert this project for the related use in SQL Server 2005.
I'm using VSTO 2008. I have modified "100" with "90".
In the SharePointListSource.cs I have an errore on row 378, statement dtsColumnMeta.MappedColumnID = dtsColumn.ID;.
DtsColumnMeta is defined ad IDTSExternalMetadataColumn. The error is about MappedColumnID.
I haven't anything online about this issue. How can I solve it? Thanks
Closed Nov 26, 2008 at 4:47 PM by kevinidzi
Released with 2008 version and code has been updated to make cross-compile easier.

comments

pscorca wrote Nov 21, 2008 at 4:26 PM

Is the statement reported for the SharePointListSource.cs? I have tried to comment it and compile the entire project: none errors have occured. So, I have copied the related dll inside the DTS\Pipeline Components folder, but when I try to use the related object in a data flow task I have this warning message: The component has inconsistent metadata. Could I have any problems by using these objects? Thanks

pscorca wrote Nov 24, 2008 at 10:28 AM

With the statement dtsColumnMeta.MappedColumnID = dtsColumn.ID commented, I have compiled the entire project with VSTO 2008, put the related object inside a SSIS 2005 project, specified for the SP List Source my URL site and list and all fuctions correctly! I will execute other proofs to confirm the correct behaviour.
But remaining two questions: a) is it possible to revert in SQL Server 2005 the MappedColumnID property? b) is it possible to use the SSIS objects with framework 2.0 (without vers. 3.5)? Thanks

kevinidzi wrote Nov 25, 2008 at 3:45 AM

pscorca:
Having inconsistent metadata is just fine. Since you recompiled it, it just needs to remap some internal things. That's fine. Sometimes it can do it by itself, sometimes you might have to just delete it and re-add it. But i'm glad you were able to get it going.

I recently had to install sql 2005 for a different project, so I will look at recompiling a sql 2005 version and run some tests shortly.

kevinidzi wrote Nov 25, 2008 at 3:48 AM

As far as 2.0 framework, that's not going to work. The subcomponent which is used to access SharePoint uses WCF, XLinq, and other things that made working with sharepoint xml easier. So that's going to require 3.5.

kevinidzi wrote Nov 26, 2008 at 4:46 PM

Released with 2008 version and code has been updated to make cross-compile easier.