Breaking up the DLL didn't seem to work. I tried rebuilding the ETL project for 4.0, but the tests didn't pass. I didn't see the test failure :) decided to take another route.
What I did was import the source for the classes that did the sql connection string lookup, build them in my project using .Net 4.0. I also changed it so rather than load connection string by name, the just take a literal connection string value. When a connection string is needed, new SqlConnection is called. The classes I need to pull into source were: InputCommandOperation, AbstractCommandOperation, and AbstactDatabaseOperation. This addressed the exception I saw. Now the exceptions I get are during write, which I suppose is progress :) Thanks for your response. I'm still open to other ideas on how to approach this. On May 12, 11:09 am, Jason Meckley <[email protected]> wrote: > that would work. the other option is to download the source code, have each > project target .net 4.0, compile and deploy. -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
