Posted by Jim Guerber on May 04, 2006 at 16:47:10: Uploaded files: 1
Comet Windows Programming with VB.NET
At the meeting in Las Vegas I showed you how to make Comet Programs using VB.NET. Here is the writeup I promised.
Steps involved in making the cb project:
1. Install VB.Net -- I use DevStudio 2003. I cannot install 2005 because of a microsoft install problem, although 2005 should work.
2. Launch visual studio
3. On the start page select New project/visual basic projects/windows Application. Type in the projsec name (CB) and select the folder under which your project folder should be created. VB.Net will create all of the project files and folders for this new project.
4. VB.net will launch the design tool with form1 visable as a blank form.
5. Note that you can select the Windows controls from the toolbox and place them on the form. By double clicking on a control you can edit the code to be executed when when the control is clicked.
6. Exit VB.net
7. In Windows explorer navigate to the folder VB.Net created for the project.
8. Copy FORM1.VB from the download replacing Form1.vb in this folder.
9. Restart VB.net.
10. Note that FORM1.VB contains ALL necessary code to describe the windows controls for the project.
11. In order to build the cb program, you must make vb.net aware of Cometlib. Click project/Add reference, select the COM tab, and select CometLib 1.0 Type Library. Click OK.
12. Build CB.EXE by clicking on Build/Rebuild Solution.
13. In Windows Explorer, navigate to the bin folder under your project folder. The two files that comprise this project are Interop.CometLib.dll and CB.exe. These files should be copied to your $(comet) folder on the CometAnywhere Host.
14. CB.EXE works in conjunction with the IB program CB.IBS. Download, and compile this program. CB.IBS builds a small file that describes the directory environment for the CometAnywhere client, Copies the two executables to the client machine and launches CB.EXE.
15. Remember that to successfully execute CB.EXE, the user must be simultaneously connected to a local Comet Session and the CometAnywhere host.