The Visual Basic .NET bindings allow you to control Bricks and Bricklets from your Visual Basic .NET programs. The ZIP file for the bindings contains:
Tinkerforge.dll
, a precompiled .NET libraryTinkerforge.xml
, the API documentation for Visual Studio, MonoDevelop, etcsource/
the source code of Tinkerforge.dll
examples/
the examples for every Brick and BrickletThe Visual Basic .NET bindings are based on the C# bindings. Since version 2.0.0 the C# bindings are CLS compliant. This allows to use them with all .NET compatible languages, such as Visual Basic .NET.
If and how the Visual Basic .NET bindings have to be installed depends heavily
on how you are going to use them. If you are just calling the Visual Basic .NET
compiler from the command line then you can just put the Tinkerforge.dll
file into the same folder as the Visual Basic .NET code of your program.
To use the bindings in an IDE you'll probably have to add the
Tinkerforge.dll
file to the assembly catalog of the IDE. How this is done
depends on the IDE and will be explained in documentation of that IDE.
To test a Visual Basic .NET example Brick Daemon and Brick Viewer have to be installed first. Brick Daemon acts as a proxy between the USB interface of the Bricks and the API bindings. Brick Viewer connects to Brick Daemon and helps to figure out basic information about the connected Bricks and Bricklets.
As an example we will compile the Stepper Brick configuration example with the Visual Basic .NET Compiler (VBNC) that comes with Mono. Create a new Visual Basic .NET project in MonoDevelop by clicking:
MonoDevelop should show an Application.vb
file in its editor. Replace its
content with the content from ExampleConfiguration.vb
file in the
examples\Brick\Stepper\
folder.
In the example HOST
and PORT
specify at which network address the
Stepper Brick can be found. If it is connected locally to USB then localhost
and 4223 is correct. The UID
value has to be changed to the UID of the
connected Stepper Brick, which you can figure out using Brick Viewer:
Const HOST As String = "localhost"
Const PORT As Integer = 4223
Const UID As String = "XXYYZZ" ' Change XXYYZZ to the UID of your Stepper Brick
Now add Tinkerforge.dll
as a reference to the project:
Tinkerforge.dll
The project is now ready for a test, click:
The Visual Basic .NET Compiler can also be used from the command line:
vbnc /target:exe /out:Example.exe /reference:Tinkerforge.dll ExampleConfiguration.vb
As an example we will compile the Stepper Brick configuration example with Microsoft Visual Basic 2010. Create a new Visual Basic project by clicking:
Visual Studio should show an Module1.vb
file in its editor. Replace its
content with the content from ExampleConfiguration.vb
file in the
examples\Brick\Stepper\
folder.
In the example HOST
and PORT
specify at which network address the
Stepper Brick can be found. If it is connected locally to USB then localhost
and 4223 is correct. The UID
value has to be changed to the UID of the
connected Stepper Brick, which you can figure out using Brick Viewer:
Const HOST As String = "localhost"
Const PORT As Integer = 4223
Const UID As String = "XXYYZZ" ' Change XXYYZZ to the UID of your Stepper Brick
Now add Tinkerforge.dll
as a reference to the project:
Tinkerforge.dll
Before the project can be tested Visual Studio needs to know the correct start object:
The project is now ready for a test, click:
Links to the API reference for the IP Connection, Bricks and Bricklets as well as the examples from the ZIP file of the bindings are listed in the following table. Further project descriptions can be found in the Kits section.