If you want to avoid having the winscp.exe as a separate file (e.g. Otherwise you need to specify an absolute path to the. The above examples assume that WinSCPnet.dll is in current working directory. %WINDIR%\Microsoft.NET\Framework64\v9\RegAsm.exe WinSCPnet.dll /codebase /tlb:WinSCPnet64.tlb %WINDIR%\Microsoft.NET\Framework\v9\RegAsm.exe WinSCPnet.dll /codebase /tlb:WinSCPnet32.tlb For these versions use RegAsm.exe from 2.0. Note that framework 3.0 and 3.5 do not ship with RegAsm.exe. You may however use any framework version from 2.0 ( v7) up.
It is recommended to use the latest available, what currently is v9. NET framework to register the assembly with. 2 On 64-bit systems, you should generally register the assembly both for 32-bit (such as old versions of Microsoft Excel) and 64-bit applications. The Framework needs to be replaced by Framework64 to register the assembly for use from 64-bit applications. Note that you can keep %WINDIR% as this environment variable should be set on your system to point to the Windows folder. In the command above, the %WINDIR% is path to your Windows installation, what is typically C:\Windows or C:\WINNT. %WINDIR%\Microsoft.NET\Framework\\RegAsm.exe WinSCPnet.dll /codebase /tlb 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 NET Standard build has some minor limitations and cannot be used with COM. 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. 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.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.įurther steps depend on a development environment/programming languages, that you will use with the assembly: 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 kommentar(er)
