Differences
This shows you the differences between the selected revisions of the page.
| 2013-05-09 | 2013-05-14 | ||
| 5.2.1 Renamed WinSCP .NET assembly to winscpnet.dll to avoid conflicts with winscp.exe (martin) | word order (martin) | ||
| Line 17: | Line 17: | ||
| E.g. If you reference WinSCP assembly from your project in Microsoft Visual Studio, it copies the assembly during build into the project //Output path// (e.g. ''<your_project_path>/obj/Debug''). Similar case is when you install the assembly into Global Assembly Cache (GAC). | E.g. If you reference WinSCP assembly from your project in Microsoft Visual Studio, it copies the assembly during build into the project //Output path// (e.g. ''<your_project_path>/obj/Debug''). Similar case is when you install the assembly into Global Assembly Cache (GAC). | ||
| - | You may want to add ''winscp.exe'' to your Visual Studio project, to have it copied to //Output path// automatically (by setting file properties //Builder action// to //None// and //Copy to Output Directory// to //Copy if newer//). //Note, in releases before the latest beta version, that it makes ''winscp.dll'' and ''winscp.exe'' to conflict. You need to rename the ''winscp.dll'' to give it a different base name, e.g. ''winscpnet.dll''. In the latest beta version, the assembly has already name ''winscpnet.dll''.// &beta | + | You may want to add ''winscp.exe'' to your Visual Studio project, to have it copied to //Output path// automatically (by setting file properties //Builder action// to //None// and //Copy to Output Directory// to //Copy if newer//). //Note that, in releases before the latest beta version, it makes ''winscp.dll'' and ''winscp.exe'' to conflict. You need to rename the ''winscp.dll'' to give it a different base name, e.g. ''winscpnet.dll''. In the latest beta version, the assembly has already name ''winscpnet.dll''.// &beta |
| ===== [[gac]] Installing to GAC ===== | ===== [[gac]] Installing to GAC ===== | ||