Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)


Topic review


Should not need to add winscp.exe to source control!

I agree with the previous request. Why can't winscp.exe be added to the lib folder rather than the content folder of the nuget package? As it stands, we either have to add winscp.exe to source control to get this to build under continuous integration, or manually modify the .csproj file as suggested above, and that will break every time the package version is updated.

RestorePackages and WinSCP

Copy to output directory can be done also on link.
My project file looks this way:

<Content Include="..\packages\WinSCP.5.7.6\content\WinSCP.exe">

I can't see the reason to copy WinSCP.exe to project file.

Re: RestorePackages and WinSCP

The WinSCP.exe is added to the project, so that Copy to Output Directory property can be set on it.

RestorePackages and WinSCP


I have set up this parameter in project file:

WinSCP is referenced in that project as nuget.

My goal is to have in source control as less info as possible.
But nuget installation of WinSCP copies file (WinSCP.exe) to project folder a add's it to project.

Nuget installation should not copy file (WinSCP.exe) to project, just add a reference to packages folder like e.g. Entity folder do:

<Reference Include="EntityFramework, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=MSIL">

Consider change of nuget installation package.