You do not need to register the assembly, if you are going to use it directly as a. If you are going to use the COM interface, register the assembly using command below. As a COM library, it needs to be registered before use. NET assembly exposes majority of its interface to COM. Using from Visual Studio or other Development or Runtime Environment VBA, VBScript, JScript, Perl: You need to register the assembly for COM.The NuGet package will even care for configuring your project to deploy the assembly. Visual Studio (C#, VB.NET): For development, you better use the NugGet package, instead of installing the assembly manually.PowerShell: No additional installations steps are needed.NET Standard build has some minor limitations and cannot be used with COM.įurther steps depend on a development environment/programming languages, that you will use with the assembly: NET Standard build of the assembly, which is located in the netstandard2.0 subfolder. NET (Core) or if you use PowerShell (Core) 6/7, you have to use. The version of WinSCPnet.dll in the root of the package is. when installing the assembly to GAC), make use of the Session.ExecutablePath property to force the assembly to look for the winscp.exe in a different location. In rare situations this is not possible (e.g. The binaries interact with each other and must be kept in the same folder for the assembly to work. The package includes the assembly itself ( winscpnet.dll) and a required dependency, WinSCP executable winscp.exe.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |