Difference between revisions of "Language - Visual Basic .NET"

From Phidgets Support
Jump to: navigation, search
 
(37 intermediate revisions by 7 users not shown)
Line 1: Line 1:
 +
<metadesc>Communicate over USB with sensors, controllers and relays with Phidgets! Our Visual Basic .NET library supports Windows using Visual Studio or Mono.</metadesc>
 
[[Category:Language]]
 
[[Category:Language]]
{{OSLang|[[File:icon-Visual Basic Net.png|64x64px|link=|alt=]]|Visual Basic .NET, developed by [http://www.microsoft.com Microsoft] is a modern object oriented programming language and the successor to [[Language - Visual Basic 6.0 | Visual Basic 6.0]].}}
+
__NOTOC__
__TOC__
+
We provide support for the Visual Basic .NET language on the Windows operating system. We also provide instructions on how to get your project started in a number of common development environments. Select your operating system and preferred development environment below, and follow the instructions to get your project running with Phidgets.
  
==Introduction==
+
If you do not know which development environment you want to use, or your development environment of choice is not listed, we recommend starting with Mono as the simplest path to getting your code running. Visual Studio is the most popular way to build Visual Basic .NET projects, but it also has a steep learning curve.
  
{{LanguageSupport|Visual Basic .NET|the complete Phidget API, including events|all Phidget devices.|the .NET or Mono framework. Both of the frameworks are supported on Windows. For Linux and OS X, only the Mono framework can be used. We provide instructions on how to set up your environment/compilers for [[#Visual Studio 2005/2008/2010 | Visual Studio 2005/2008/2010]], [[#Visual Studio 2003 | Visual Studio 2003]], [[#MonoDevelop | MonoDevelop]] and the [[#Mono | Mono command line compilers]]|}}
+
Once you have set up your development environment to run with Phidgets, we recommend you follow our guide on [[Phidget Programming Basics]]. The guide will showcase the fundamentals of programming with Phidgets.
  
==Quick Downloads==
+
==Choose Your Development Environment:==
{{QuickDownloads|Visual Basic .NET|
+
{{APIQuickDownloads|http://www.phidgets.com/documentation/Phidget21.NET.zip .NET}}|
+
{{ExampleQuickDownloads|http://www.phidgets.com/downloads/examples/VBNET.zip|}}|
+
{{ExtraLibraryQuickDownloads|http://www.phidgets.com/downloads/libraries/phidget21-x86.zip|.NET Framework Files|}}
+
{{WindowsQuickDownloads}}
+
}}
+
  
==Getting started with Visual Basic .NET==
+
{{Language_-_Visual_Basic_.NET_Dev_Environment_Table}}
  
If you are new to writing code for Phidgets, we recommend starting by running, then modifying existing examples. This will allow you to:
+
== Quick Downloads ==
{{ExampleCodeReasons}}
+
If you already know what you're doing and just need the files, you can find them all below.
  
Instructions are divided up by operating system. Choose:
+
=== Documentation ===
*[[#Windows(2000/XP/Vista/7)|Windows 2000 / XP / Vista / 7]]
+
*[[#OS X |OS X]]
+
*[[#Linux | Linux]] (including PhidgetSBC)
+
  
==Windows (2000/XP/Vista/7)==
+
*{{Phidget22API}} (Select Visual Basic .NET from drop-down menu)
  
===Description of Library Files===
+
=== Example Code ===
Visual Basic .NET programs on Windows depend on the following files, which the installers above put onto your system:
+
* <b>{{Code|phidget21.dll}}</b> contains the actual Phidget library, which is used at run-time.  By default, it is placed in {{Code|C:\Windows\System32}}.
+
You will also need one of the following two files, depending on the .NET framework version you are targeting:
+
* <b>{{Code|Phidget21.NET.dll}}</b> is the Phidget library for .NET framework <i><b>2.0</b></i> or higher. Your compiler has to know where this file is. By default, it is placed into {{Code|C:\Program Files\Phidgets}}. You can either point your compiler to that location, or copy and link to it in a directory for your project workspace.
+
* <b>{{Code|Phidget21.NET1.1.dll}}</b> is the Phidget library for .NET framework <i><b>1.1</b></i>. Your compiler has to know where this file is. By default, is is placed into {{Code|C:\Program Files\Phidgets}}. You can either point your compiler to that location, or copy and link to it in a directory for your project workspace.
+
You can optionally install the following files:
+
* <b>{{Code|Phidget21.NET.XML}}</b> provides the IntelliSense in-line documentation for the .NET library in Visual Studio/MonoDevelop. This documentation is also visible in the Object Browser in Visual Studio. By default, it is placed into {{Code|C:\Program Files\Phidgets}}.
+
* <b>{{Code|Policy.2.1.Phidget21.NET.dll}}</b> is the policy assembly for {{Code|Phidget21.NET.dll}}. Our installer places this file in the Global Assembly Cache(GAC) directory. It directs any programs compiled against version 2.1.0 or higher of {{Code|Phidget21.NET.dll}} to use the most recent installed version.
+
  
If you do not want to use our installer, you can download the five [http://www.phidgets.com/downloads/libraries/Phidget21-windevel.zip files].
+
*{{SampleCode|VBNET|Visual Basic .NET Examples}}
  
 +
===Libraries===
  
Running the examples and writing your own code can be fairly environment-specific, so we include instructions for [[#Visual Studio 2005/2008/2010 | Visual Studio 2005/2008/2010]], [[#Visual Studio 2003 | Visual Studio 2003]], [[#MonoDevelop | MonoDevelop]] and the [[#Mono | Mono command line compiler]].
+
{{AllQuickDownloads}}
 
+
===Visual Studio 2005/2008/2010===
+
 
+
Microsoft makes free versions of Visual Studio available known as Express Editions.  The Express editions are suitable for most applications, but are limited in features for more complex applications. Please see [http://www.microsoft.com/visualstudio Microsoft Visual Studio] for more information.
+
 
+
=====Use Our Examples=====
+
 
+
Please start by downloading the [http://www.phidgets.com/downloads/examples/VBNET.zip examples] and unpack them into a folder.  While these examples were written in Visual Studio 2005 and Visual Studio 2008, Visual Studio 2010 will easily open and upgrade them with the Visual Studio Conversion Wizard.
+
 
+
[[File:VS2005 Conversion Wizard.PNG|link=|alt=Conversion Wizard]]
+
 
+
To load all projects in Visual Studio, go to File &rarr; Open &rarr; Project, and open {{Code|AllExamples/AllExamples.sln}} or {{Code|AllExamples/AllExamples_vs2008.sln}} for Visual Studio 2005 and 2008, respectively.
+
 
+
This will load all of the examples available for Visual Basic .NET, and then you can set your main project to be the HelloWorld project that will work with any Phidget board.  Or you can choose the example that matches your device.  {{FindYourDevice}}
+
 
+
The only thing left to do is to run the examples! Click on Debug &rarr; Start Debugging. Please note that the projects, by default try to find the {{Code|Phidget21.NET.dll}} in {{Code|C:\Program Files\Phidgets}}. If you have it installed in another location, please change the path to the file's location accordingly. If you are receiving an error message regarding that the type Phidget is not defined, please re-add the reference to {{Code|Phidget21.NET.dll}}. Please see the [[#Write Your Own Code | Write Your Own Code ]] section for details.
+
 
+
[[File:VBNET VS2005 Run.PNG|link=|alt=Run]]
+
 
+
Once you have the Visual Basic .NET examples running, we have a [[#Follow the Examples|teaching]] section below to help you follow them.
+
 
+
=====Write Your Own Code=====
+
 
+
When you are building a project from scratch, or adding Phidget function calls to an existing project, you'll need to configure your environment to properly link the Phidget .NET library. To begin:
+
 
+
1. Generate a new Visual Basic .NET Console Application project with a descriptive name such as PhidgetTest.
+
 
+
[[File:VBNET VS2005 New Project.PNG|link=|alt=New Project]]
+
 
+
2. Add a reference to the Phidget .NET library.
+
 
+
[[File:VBNET VS2005 Add Reference 1.PNG|link=|alt=Add Reference]]
+
 
+
3. Under the .NET tab, select {{Code|Phidget21.NET.dll}}.
+
If you used our installer, these files are installed in {{Code|C:\Program Files\Phidgets}}, by default. If it does not appear in this list, then you can browse to the Phidget Framework installation directory and add the file.
+
 
+
[[File:VBNET VS2005 Add Reference 2.PNG|link=|alt=Add Reference]]
+
 
+
The project now has access to the Phidget function calls and you are ready to begin coding.
+
 
+
The same [[#Follow the Examples|teaching ]] section which describes the examples also has further resources for programming your Phidget.
+
 
+
===Visual Studio 2003===
+
 
+
=====Use Our Examples=====
+
 
+
As the Visual Basic .NET examples were written in Visual Studio 2005 and 2008, Visual Studio 2003 is not able to open the examples. Furthermore, it will be difficult to import the examples into your Visual Studio 2003 project as you will need to recreate the GUI components. Fortunately, taking a look at the source code will give you valuable programming insight. We have a [[#Follow the Examples|teaching ]] section below to help you follow them.
+
 
+
=====Write Your Own Code=====
+
 
+
When you are building a project from scratch, or adding Phidget function calls to an existing project, you'll need to configure your development environment to properly link the Phidget .NET library.
+
 
+
1. Generate a new Visual Basic Console Application project with a descriptive name such as PhidgetTest.
+
 
+
[[File:VBNET VS2003 New Project.PNG|link=|alt=New Project]]
+
 
+
2. Add a reference to the Phidget .NET library.
+
 
+
[[File:VBNET VS2003 Add Reference 1.PNG|link=|alt=Add Reference]]
+
 
+
3. Under the .NET tab, select {{Code|Phidget21.NET1.1.dll}}.
+
If you used our installer, these files are installed in {{Code|C:\Program Files\Phidgets}}, by default. If it does not appear in this list, then you can browse to the Phidget Framework installation directory and add the file.
+
 
+
[[File:VBNET VS2003 Add Reference 2.PNG|link=|alt=Add Reference]]
+
 
+
The project now has access to the Phidget21 function calls and you are ready to begin coding.
+
 
+
The [[#Follow the Examples|teaching ]] section also has further resources for programming your Phidget.
+
 
+
===Mono===
+
 
+
This section will provide instructions on how to compile using the {{Code|vbnc}} compiler.
+
 
+
=====Use Our Examples=====
+
 
+
We do not have Visual Basic .NET examples for the Mono framework. Fortunately, you can take a look at the source code for our [http://www.phidgets.com/downloads/examples/CSharp.zip Visual Studio 2005 and 2008 examples] for valuable programming insight. We have a [[#Follow the Examples|teaching ]] section below to help you follow them.
+
 
+
=====Write Your Own Code=====
+
 
+
When you are building a project from scratch, or adding Phidget function calls to an existing project, you'll need to configure your compiler to properly link the Phidget .NET library.
+
 
+
Place the {{Code|Phidget21.NET.dll}} in the same directory as your source code.
+
To compile and build an executable, run:
+
<div class="source">
+
<syntaxhighlight lang=bash>
+
vbnc /out:example.exe /r:Phidget21.NET.dll Example.vb
+
</syntaxhighlight>
+
</div>
+
 
+
Afterwards, you will have an executable named {{Code|example.exe}} that you can run. Type the following to run the program:
+
<div class="source">
+
<syntaxhighlight lang=bash>
+
mono example.exe
+
</syntaxhighlight>
+
</div>
+
 
+
The [[#Follow the Examples|teaching]] section also has further resources for programming your Phidget.
+
 
+
===MonoDevelop===
+
 
+
=====Use Our Examples=====
+
 
+
Download the [http://www.phidgets.com/downloads/examples/VBNET.zip examples] and unpack them into a folder. Here, you can find example programs for all the devices, as well as a HelloWorld program that will run with any Phidget.
+
 
+
These examples were written in Visual Studio 2005 and 2008, but they are also compatible with MonoDevelop. Please note that the examples are only designed to be run under the .NET framework. The examples are not compatible with the Mono framework. Despite this, if you are using the Mono framework, you can use the code within the examples for valuable programming insight.
+
 
+
The rest of this section will explain the steps needed to run our examples under the .NET framework. To load all projects in MonoDevelop, go to File &rarr; Open, and open {{Code|AllExamples/AllExamples.sln}}
+
 
+
This will load all of the examples available for Visual Basic .NET, and then you can set your main project to be the one that matches your device.  {{FindYourDevice}}
+
 
+
[[File:VBNET Win MonoDevelop Startup Project.PNG|link=|alt=Start Up Project]]
+
 
+
The only thing left to do is to run the examples! Right click the project, and click on {{Code|Run With}} and select the Microsoft .NET framework. Please note that the projects, by default try to find the {{Code|Phidget21.NET.dll}} in the {{Code|C\Program Files\Phidgets}}. If you have it installed in another location, please change the path to the file's location accordingly. If you are receiving an error message regarding that the Phidget is not defined, please re-add the reference to {{Code|Phidget21.NET.dll}}. Please see the [[#Write Your Own Code 4 | Write Your Own Code]] section for details.
+
 
+
[[File:VBNET Win MonoDevelop Run.PNG|link=|alt=Run]]
+
 
+
Once you have the Visual Basic .NET examples running, we have a [[#Follow the Examples|teaching]] section below to help you follow them.
+
 
+
=====Write Your Own Code=====
+
 
+
When you are building a project from scratch, or adding Phidget function calls to an existing project, you'll need to configure your  development environment to properly link the Phidget .NET library. To begin:
+
 
+
1. Create a new Visual Basic .NET console project with a descriptive name such as PhidgetTest.
+
 
+
[[File:VBNET Win MonoDevelop New Project.PNG|link=|alt=New Project]]
+
 
+
2. Add a reference to the Phidget .NET library.
+
 
+
[[File:VBNET Win MonoDevelop Add Reference 1.PNG|link=|alt=Add Reference]]
+
 
+
3. Select {{Code|Phidget21.NET.dll}}. If you used our installer, by default, this file is placed in {{Code|C:\Program Files\Phidgets}}. If it is in another location, please change the path to the file's location accordingly.
+
 
+
[[File:VBNET Win MonoDevelop Add Reference 2.PNG|link=|alt=Add Reference]]
+
 
+
The project now has access to the Phidget function calls and you are ready to begin coding.
+
 
+
The same [[#Follow the Examples|teaching]] section which describes the examples also has further resources for programming your Phidget.
+
 
+
==OS X==
+
 
+
Visual Basic .NET has excellent support on OS X through the Mono framework.
+
 
+
The first step in using Visual Basic .NET on Mac is to install the Phidget libraries.  Compile and install them as explained on the [[OS - OS X]] page, which also describes the different Phidget files, their installed locations, and their roles....
+
 
+
==Linux==
+
 
+
Visual Basic .NET has support on Linux through the Mono framework. 
+
 
+
===Use Our Examples===
+
+
The first step in using Visual Basic .NET with Phidgets on Linux is to install Mono.  Although you probably have already done this if you're a Visual Basic .NET programmer, you want to make sure you have all of the packages you'll need.  Try:
+
 
+
<div class="source">
+
<syntaxhighlight lang=bash>
+
sudo apt-get mono-complete
+
</syntaxhighlight>
+
</div>
+
 
+
The Visual Basic Mono framework also requires the Visual Basic .NET compiler, {{Code|vbnc}}.  This can be installed via another Mono package:
+
 
+
<div class="source">
+
<syntaxhighlight lang=bash>
+
sudo apt-get install mono-vbnc
+
</syntaxhighlight>
+
</div>
+
 
+
Next, you'll want to install the main Phidget Libraries.  Compile and install them as explained on the main [[OS - Linux | Linux page]].  That Linux page also describes the different Phidget files, their installed locations, and their roles.
+
 
+
Then, you will need the Phidget .NET libraries.  These are part of the Windows library zip file download:
+
 
+
* [http://www.phidgets.com/downloads/libraries/Phidget21-windevel.zip Phidget Windows Library Zip File]
+
 
+
Extract the library zip file.  Descriptions for the files are available on the [[OS - Windows]] page, but for now we only need the {{Code|Phidget21.NET.dll}} file to run the Phidget Visual Basic examples in Mono.  So remember where you unzipped these Windows libraries - you will need to copy the {{Code|Phidget21.NET.dll}} file into your example directory shortly.
+
 
+
Next, you'll want to download and extract the Phidget Visual Basic .NET Examples (not the ones for .NET Compact):
+
 
+
* [http://www.phidgets.com/downloads/examples/VBNET.zip Visual Basic .NET Examples for Windows]
+
 
+
To check that your Linux, Phidget, and Mono setup is all working together, you'll want to run the Visual Basic (VB) examples.  You'll probably want to start with the Hello World VB example.  Alternatively, you could find the source code for your device. {{Template:FindYourDevice}}
+
 
+
All of the .NET examples are much larger projects through Visual Studio, so you'll need to dig around within the project and find the source code and compile only that source code using Mono.
+
 
+
Let's say you're running the Hello World example.  The source code for the example is in the directory:
+
 
+
:{{Code|VBNET/}} &rarr; {{Code|Hello World/}} &rarr; {{Code|Module1.vb}}
+
 
+
Other examples will be in directories named appropriately for their software object name, rather than {{Code|Hello World}}.  Once you have found the example you want to run, copy the {{Code|Phidget21.NET.dll}} file that you unzipped earlier into that example directory where the {{Code|Module1.vb}} file is. 
+
 
+
Then, compile the code.  When compiling, you need to link to the Phidget library. As the Phidget21.NET file is an "additional assembly" in Visual Basic/Mono, you can link to the assembly using the {{Code|-r}} "reference" switch:
+
 
+
<div class="source">
+
<syntaxhighlight lang=bash>
+
vbnc Module1.vb -r:Phidget21.NET.dll
+
</syntaxhighlight>
+
</div>
+
 
+
This will compile a {{Code|*.exe}} file - in this case, {{Code|Module1.exe}}.  This you can then run under Mono:
+
 
+
<div class="source">
+
<syntaxhighlight lang=bash>
+
sudo mono Program.exe
+
</syntaxhighlight>
+
</div>
+
 
+
Remember that the {{Code|sudo}} is needed unless you have your [[OS - Linux#Setting udev Rules|udev rules set on your Linux system]].
+
 
+
If you will be compiling with an IDE such as GTK# or MonoDevelop, we don't have explicit instructions by IDE for Linux.  However, you will probably find the [[#MonoDevelop | MonoDevelop]] section in the Windows portion above useful.
+
 
+
===Write Your Own Code===
+
 
+
When writing your code from scratch, you start it as you would any Visual Basic code on Linux, such as within a text editor like Emacs, Vi, Gedit, or Kate. In your .vb source code file, you must include a reference to the Phidget software object.  In the case of a Phidget interface kit device, this would look like:
+
 
+
<div class="source">
+
<syntaxhighlight lang=vbnet>
+
Public Class Form1
+
  'The Phidget object declaration
+
+
  Dim WithEvents ifKit As Phidgets.InterfaceKit
+
+
  '... Form1_Load and Form1_OnClosing here
+
End Class
+
</syntaxhighlight>
+
</div>
+
 
+
For other devices, check the API for your device on our webpage for the software object name, and the [http://www.phidgets.com/documentation/Phidget21.NET.zip API for .NET] for the specific syntax to use.  Then, you would compile your completed VB code the same way as the examples above.
+
 
+
Mono also has a few different IDEs which you can use to develop code, and these are especially useful if you are doing GUI development.  We provide instructions for MonoDevelop - one such IDE - being used [[#MonoDevelop|under Windows]].
+
 
+
To learn how to write your own code for your Phidget, and to learn more about our API, we have a [[#Follow the Examples|teaching section]] to help you follow the provided VB examples and which has resources such as the API reference.
+
 
+
==Follow the Examples==
+
 
+
By following the instructions for your operating system and compiler above, you probably now have a working example and want to understand it better so you can change it to do what you want.  This teaching section has resources for you to learn from the examples and write your own.
+
 
+
Your main reference for writing Visual Basic .NET code will be our .NET API information, with syntax for all of our functions:
+
 
+
{{UsingAPhidgetInCodeGeneral|both of which are available in .NET|[http://www.phidgets.com/documentation/Phidget21.NET.zip .NET API]}}
+
 
+
===Example Flow===
+
 
+
{{ExamplePseudocode|In Visual Basic .NET, you can name these '''event''' functions whatever you like, although you must catch the events by name in the "Handles" portion of the function declaration.  The "Handles" portion of the function hooks them into the actual events when they occur. See our examples for details.<br>
+
In the example code, the event functions common to all Phidgets are called things like '''AttachHandler()''' and '''DetachHandler()''', etc.<br><br>
+
Some event functions will be specific to each device, like when a tag is read on an RFID board, or when a sensor value changes on an Interface Kit.
+
Other functions are given in the device-specific examples to show you more detail on using your Phidget. 
+
|Creating a Phidget software object in Visual Basic .NET is specific to the Phidget.  For a Phidget Spatial, for example, this would involve creating a {{Code|Spatial}} object.  The examples show how to do this and other API functions.<br><br>
+
The object provides device specific methods and properties which are available from the API for your specific Phidget.|
+
[http://www.phidgets.com/documentation/Phidget21.NET.zip .NET API]}}
+
 
+
===Code Snippets===
+
 
+
Specific calls in Visual Basic (VB) .NET will differ in syntax from those on the [[General Phidget Programming]] page, but the concepts stay the same.  
+
 
+
It may help to have the [[General Phidget Programming]] page and this section open at the same time, because they parallel each other and you can refer to the VB .NET syntax.  However, ''many'' additional concepts are covered on the General Phidget Programming page on a high level, such as using multiple Phidgets, handling errors, and different styles of programming.
+
 
+
====Step One: Initialize and Open====
+
 
+
The open() function opens the software object, but not hardware. So, it is not a guarantee you can use the Phidget immediately.
+
 
+
The different types of open can be used with parameters to try and get the first device it can find, open based on its serial number, or even open across the network. The API manual lists and [[General Phidget Programming]] discusses all of the available modes that open provides.
+
 
+
For example, if we were using an Interface Kit Phidget board as our device, the create and open calls would look like this:
+
 
+
<div class="source">
+
<syntaxhighlight lang=vbnet>
+
ifKit = New Phidgets.InterfaceKit
+
ifKit.open()
+
</syntaxhighlight>
+
</div>
+
 
+
====Step Two: Wait for Attachment (plugging in) of the Phidget====
+
 
+
To use the Phidget, it must be plugged in (attached). We can handle this by using event driven programming and tracking the AttachEvents and DetachEvents, or we can handle this by calling waitForAttachment. This function works for any Phidget. WaitForAttachment will block indefinitely until a connection is made to the Phidget, or an optional timeout is exceeded.
+
 
+
When combined in your initialization function with the initialization and open from above, the wait for attachment would look like this:
+
 
+
<div class="source">
+
<syntaxhighlight lang=vbnet>
+
Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs)
+
Handles MyBase.Load
+
    ifKit = New Phidgets.InterfaceKit
+
    ifKit.open()
+
    ifKit.waitForAttachment(3000)
+
End Sub
+
</syntaxhighlight>
+
</div>
+
 
+
====Step Three: Do Things with the Phidget====
+
 
+
We recommend the use of event driven programming when working with Phidgets. In VB.NET we can hook an event handler into the event of a sensor changing on an Interface Kit board with the following code:
+
 
+
<div class="source">
+
<syntaxhighlight lang=vbnet>
+
Private Sub ifKit_SensorChange(ByVal sender As Object, ByVal e As Phidgets.Events.SensorChangeEventArgs) Handles ifKit.SensorChange
+
    TextBox1.Text = "Index " + e.Index.ToString() + " Value: " + e.Value.ToString()
+
End Sub
+
</syntaxhighlight>
+
</div>
+
 
+
With this function, the code inside ifKit_SensorChange will get executed every time the Phidget Interface Kit reports a change on one of its analog inputs. This is because it "Handles" the SensorChange event.  Some events such as Attach and Detach belong to the base Phidget object and thus are common to all types of Phidgets.
+
 
+
Some values can be read and sent directly to the Phidget, simply use the instance members and properties. This is also how you would set properties on the Phidget such as the output state or
+
sensor sensitivity.  For example, obtaining the value of analog input (sensor) 0 on an Interface Kit board would be via:
+
 
+
<div class="source">
+
<syntaxhighlight lang=vbnet>
+
Dim val As Integer = ifKit.sensors(0).Value
+
</syntaxhighlight>
+
</div>
+
 
+
====Step Four: Close and Delete====
+
 
+
At the end of your program, unhook any events and call Application.DoEvents(). This will make sure there are no outstanding events being processed before calling close.
+
 
+
<div class="source">
+
<syntaxhighlight lang=vbnet>
+
Private Sub Form1_FormClosing(ByVal sender As Object, ByVal e As System.Windows.Forms.FormClosingEventArgs) Handles Me.FormClosing
+
    RemoveHandler ifKit.SensorChange, AddressOf ifKit_SensorChange
+
    Application.DoEvents()
+
    ifKit.close()
+
End Sub
+
</syntaxhighlight>
+
</div>
+
 
+
{{MoreHowTos}}
+
 
+
The ''complete'' set of functions you have available for all Phidgets can be found in the [http://www.phidgets.com/documentation/Phidget21.NET.zip .NET API].  You can also find more description on any device-specific function in the Device API page for your specific Phidget, which can be found on its product page on our [http://www.phidgets.com main website].
+
 
+
==Common Problems and Solutions/Workarounds==
+
 
+
None yet.
+

Latest revision as of 22:15, 28 February 2019


We provide support for the Visual Basic .NET language on the Windows operating system. We also provide instructions on how to get your project started in a number of common development environments. Select your operating system and preferred development environment below, and follow the instructions to get your project running with Phidgets.

If you do not know which development environment you want to use, or your development environment of choice is not listed, we recommend starting with Mono as the simplest path to getting your code running. Visual Studio is the most popular way to build Visual Basic .NET projects, but it also has a steep learning curve.

Once you have set up your development environment to run with Phidgets, we recommend you follow our guide on Phidget Programming Basics. The guide will showcase the fundamentals of programming with Phidgets.

Choose Your Development Environment:

Visual Basic .NET Development Environments
OS - Windows Windows

C VS WIN.png C VS WIN on.png

CS MONO WIN.png CS MONO WIN on.png

Quick Downloads

If you already know what you're doing and just need the files, you can find them all below.

Documentation

Example Code

Libraries