This is the very first tutorial for SocketPro.

1. SocketPro Installation program is simple.
2. SocketPro automatically set all 32bit dlls for you.
3. It doesn’t register 64bit COM dlls.
4. It doesn’t distribute 64bit server dlls into window system directory.
5. We need to manually register 64bit COM dlls and distribute 64bit server dlls into window system directory.
6. First of all, create a directory x64 for storing all of 64bit dlls.
7. Use DOS command with administrator privilege to register three 64bit COM dlls.
8. Register 64bit COM npUSocket.dll by regsvr32 npUSocket.dll.
9. Register 64bit COM udb.dll by regsvr32 udb.dll.
10. Register 64bit COM ufile.dll by regsvr32 ufile.dll.
11. Copy three 64bit dlls, usktpror.dll, uodbsvr.dll and ufilesv into window system directories.
12. Here is a table listing all of important libraries.

	Client side	Server Side
SocketPro core library	npUSocket.dll (COM)	usktpror.dll
Remote database service through MS OLEDB	udb.dll (COM)	uodbsvr.dll
SocketPro adapter for .NET	SProAdapter.dll	SProAdapter.dll
COM interop library for npUSocket.dll	usocketnet.dll	usocketnet.dll
COM interop library for udb.dll	udbnet.dll	udbnet.dll
Windows remote file management	UFile.dll (COM)	Ufilesvr.dll

13. If your development language is C++, you use the top two libraries only in general.
14. If your development environment is .NET, usually you need to use the middle three libraries. Also, you have to reference the libraries sproadpater.dll and usocketnet.dll for both client and server projects.
15. Very occasionally, you may use our window remote file management service.
16. Next, put 32bit SocketPro .NET adapter into .NET global assembly cache by executing gacutil.exe /i Sproadapter.dll.
17. Put 64bit SocketPro .NET adapter into .NET global assembly cache by executing gacutil.exe /i x64\Sproadapter.dll. Doing so will simplify your .NET development.
18. Start remoteconnector, which is a 32bit window service and runs on the port 17001. Many of sample and tutorial applications will use it as a testing SocketPro server.
19. Start visual studio 2005 and open csharp tutorial one solution.
20. Note both client and server reference SproAdapter (SocketPro adapter for .NET) and usocketnet.dll (COM interoping library between .NET and native code npUSocket.dll).
21. Compile csharp tutorial one with visual studio 2005 for both 64- and 32-bit applications.
22. Test both client and server applications for both 32- and 64-bit versions.
23. Start visual studio 2010, open csharp tutorial one solution and convert 2005 solution into 2010 solution.
24. Set both client and server projects with target .NET runtime 4.0 for all of platforms
25. Open file app.config for both client and server, and add useLegacyV2RuntimeActivationPolicy="true"
26. Compile csharp tutorial one solution with 2010.
27. Test both client and server applications for both 32- and 64-bit versions.
28. Start ODBClient.exe and connect it to remoteconnector with port 17001.
29. Click the buttons Connect and To Data Source.
30. NWIND.mdb is an access northwind database. For the simplicity, we use it for testing database accessing from a 32bit SocketPro server application. Note you can NOT access it from a 64bit server application because there is no 64bit driver available. You can use MS Access to open the file and see what tables the database contains.
31. Execute sql statement “select * from orders” by clicking the button Execute SQL
32. Execute sql statement “select * from orders, employees” by clicking the button Execute SQL

Because we don’t see any problems here, we are sure that all of libraries are running correctly. Therefore, we are ready to move to the next tutorial now.