advice as i migrate my winscp based ssis pkg to our prod server

• stan

  Ten Centuries

  Points: 1366

  More actions

  March 27, 2026 at 6:54 pm

  #4756542

  Hi , i installed winscp on my pc, added it to GAC thru vs (i think a developer script) on my pc as well, and added a reference to it while editing a c# script in vs in the pkg i was developing.  It might have been on 2 c# scripts.

  I just deployed the pkg to our production dw server, specifically to the catalog.   I think i can muddle thru the winscp install there using default c: drive as a target.   my friend thinks the .dll reference(s) from c# were deployed automatically, im not so sure.   Is that how it works?   Or do i need to add references again?

  im  most concerned about adding winscp to GAC there on the prod server.  My only experience is doing that thru vs, specifically a developer script window i think.     For starters vs isnt installed there.   I could probably install vs there if i had to.  does the community have any advice?   For the moment i cant imagine installing winscp to GAC there remotely (from my pc) but i'd have to look at the command again.

  • This topic was modified 1 hours, 5 minutes ago by stan.
  • This topic was modified 1 hours, 4 minutes ago by stan.
  • This topic was modified 1 hours, 1 minutes ago by stan.