| |
Hi,
Here is my first attempt to build a VB.NET DLL class to facilitate somehow the
building of VB.NET programs that talk to the old ControlLab Interface "B",
70909.
http://www.box.net/shared/xc44rksi2h
This folder includes Source files and also setup files.
To RUN the DEMO applications you need Microsoft .NET Framework 3.5 SP1 (FREE)
already installed on your PC.
To use the Source, you need Vusal Basic .NET 2008 Express Edition. (FREE)
I am not a VB.NET expert and this project is also a learning opportunity for me.
This is not a ControlLab programming language. I use VB.NET as the programming
language to make Programs that Reads the Interface Inputs (Switch,
Light/Temp./Rotation Sensors) and Writes to Interface Outputs (Motors,
Lights...). The DLL is just a black box that manages the Serial Communication
and implements the required protocol for the interface and provide methods and
properties for easy access through a main program.
I supplied all sources. The simplest program to look at the source to get
familiar is the demo2 which activates a motor on output 1 when a limit switch is
pressed on input 1, motor stops if the switch is not pressed.
The DEMO2 has a reference to the Lego70909ClassLib.dll...
I did not yet wrote a document that explains how to use it. But I will
eventually write it. Meanwhile, if you know a little about VB or VBA or VB.NET,
you will probably find your way by yourself.
I did not make a lot of testing on another computer so I am not sure it has all
files needed... Please let me know.
I tested only on Windows XP sp3. No idea if it will run on a Vista or win7 or
2000.
Since I don't have more than one interface, I don't know if it can really handle
2 or more controlLab interface. Some feedback would be appreciated on this
matter.
I am using a Prolific USB to RS232 adaptor which works great.
Here is a quick start to build your own controllab program with the use of the
DLL in VB.NET.
1- Start VB.NET 2008 express edition, and start a new Project and select a
Windows Form Application template.
2- In "Project" Menu, select "Add Reference"
3- Go to "Browse" TAB and select the Lego70909ClassLib.DLL that is part of the
Lego70909ClassLibSource.zip in folder
...Lego70909ClassLib\Lego70909ClassLib\bin\Release
4- On the Form (Form1 if you did not rename it), drag a Timer control from the
toolbox on the left (Part of the "Components" folder in the toolbox).
5- This timer will execute a sub routine at a certain scan time you supply.
6- Double clicking on the form will bring you on the code page related to the
form and will automatically create the first subroutine we need wich is the
Form1_Load that will execute as soon as your application start.
7- In this code windows, just before the "Public Class Form1" (General
Declaration region), write: Imports LegoControlLab
This is to get an easier access to the lego70909 methods and properties etc...
8- Always in the code window, right below "Public Class Form1", write:
Dim lego1 As New Lego70909
This is to create an object from the DLL representing a ControlLab Interface
If you have two interfaces (and 2 serial ports) then you would write:
Dim lego1 As New Lego70909
Dim lego2 As New Lego70909
9- Inside the "Form1_Load" subroutine (Just under "Private Sub Form1_Load"),
write the following lines:
lego1.ComPort = "Com2" 'Tells the DLL which com port is used for the interface
lego1.StartLego() 'To Start Communicating with the interface
Me.Timer1.Interval = 50 'Configue the Timer we added to the form (Step
4) at 50 ms (quite fast)
Me.Timer1.Enabled = True 'Starts the Timer
10- Go back to the Form (Form1.vb [Design]) and double-click on the timer1
control at the bottom of the screen. This will create automatically the
Timer1_Tick Subroutine in the form Code window.
11- In the form code window, inside the timer1_tick sub, you actually program
your Lego ControlLab application.
Write the following lines inside the timer1_tick subroutine:
'At the beginning, you must get the actual status of the imputs.
lego1.GetInputs()
If lego1.InputPressed(1) Then
lego1.Out_OnR(1) 'Start motor on output 1 right direction (Right LED
on Output 1 goes ON )
Else
lego1.Out_Off(1) 'Stop and Brake motor on output 1. Use Out_Free(1)
instead if you want the motor to stop without braking.
End If
12- Last step to our first controlLab application, is to stop the interface if
when we close our form. In the form1 code window, there are two combo box on
the top, in the first combobox, select "(Form1 Events)" and in the second
combobox, select "FormClosing". This will create automatically the subroutine
"Form1_FormClosing" that will execute we close our application during runtime.
13- Inside the Form1_FormClosing subroutine, write the following lines:
If Not (lego1 Is Nothing) Then
If lego1.IsStarted Then
lego1.StopLego()
Do While lego1.IsStarted
' Wait until IsStarted = False (Waiting for Lego Read Inputs
thread to be stopped)
Loop
End If
lego1 = Nothing
End If
14- Done. Save you application. Go to Debug menu and select "Start Debugging"
to test your application. Press Switch one connected on input 1 of the
controlLab interface, the motor on output "A" should start. Release Switch to
stop motor.
There are many Methods (To command outputs) and properties. I will try to
describe them in details in a document I will put in the Folder URL...
For now, you can browse them using the View menu, Object Browser, Browse "My
Solution", Lego70909ClassLib, LegoControlLab, Lego70909 then look on the Right
pane...
All method to control outputs start with Out_ for one port control (You have to
supply the port number) and OutM_ for multiple port control. For the OutM_
methods, you must supply a byte (8 bits) where each bit correspond to a Port.
Use Hexadecimal annotation (&H).
To turn on Output 1 and 5 = 00010001, use Lego1.OutM(&H11), for out 1,2,7 =
01000011, use Lego1.OutM(&H43)
For switch status use property InputPressed(PortNum). This will return True if
switch is pressed, False if not pressed.
For light and Temperature sensor, use InputValue(PortNum).
For Rotation sensor, use RotationCount(PortNum) to Get/Set the rotation count
(16 count per turn). Lego1.RotationCount(5) = 0 will reset the count of port 5.
For rotation sensor, there is also the properties: RotationCW (true if turning
clockwise, False otherwise), RotationSpeed: thise is for information. 0= no
moves, 1 turning slow, 2=fast, 3 is very very fast...
This is a work in progress.
Thank you for your feedback.
Yves Levesque.
|
|
| |
In lugnet.dacta, Yves Levesque wrote:
> Hi,
>
> Here is my first attempt to build a VB.NET DLL class to facilitate somehow the
> building of VB.NET programs that talk to the old ControlLab Interface "B",
> 70909.
>
>
> Yves Levesque.
Thanks for posting your program for others to share. I will try and make some
time to test it out. It is becoming quite rare to see others using these
interfaces.
I have multiple 9751 ControlLab interfaces and could do some testing using more
than one at a time. I currently do not have VB installed at this time.
Do you have any sample programs setup for multiple CLIs that I could test for
you?
Thanks again.
Brian
|
|
| |
In lugnet.dacta, Brian Bachmeier wrote:
>
> Thanks for posting your program for others to share. I will try and make some
> time to test it out. It is becoming quite rare to see others using these
> interfaces.
> I have multiple 9751 ControlLab interfaces and could do some testing using more
> than one at a time. I currently do not have VB installed at this time.
> Do you have any sample programs setup for multiple CLIs that I could test for
> you?
> Thanks again.
> Brian
Hi Brian, I will prepare a simple installable demo that will support multiple
Interfaces. I will transfer it soon to the same url of the other demo and
source files from my first post.
Indeed, this interface is pretty old. But for fixed automated project layout,
it is still interresting especially if we can take control of multiple CLIs for
big layout. The quantity of IOs is the main interest. And a PC makes a much
more powerfull brain than an RCX or NXT. It is supporting all 9V devices
(motors, switch, rotation and other sensors), the same as the RCX.
BTW, I tested the two installable demos already posted, in my brother's PC which
has Win7 and everything is working.
I did not yet finished the error trapping. This is only a first version...
Thank you for your interest. I am looking forward to hear from your test
results.
Yves.
|
|
| |
Hi,
I just added a demo file in the folder http://www.box.net/shared/xc44rksi2h.
It is called LegoMultiCLISetup.zip and contains the installable test application
for multiple (Max 3) CLIs.
I would appreciate if someone could try it with 2 or 3 CLIs at the same time and
give me some feedback. I have only one CLI and cannot test this Multiple CLI
control feature.
Once installed, start the application, Select Com ports for the CLIs that are
connected to your PC. Don't forget to put a "Checkmark" to the port you want to
use.
Press Start CLIs. Pressing a Switch on port1 of any CLI will start motors on
port 1 of other CLIs. Release the switch to stop motor(s).
Ex., If you use 3 CLIs, pressing a Switch on Port 1 of of CLI#1 will start
Motors on port 1 of CLI#2 and CLI#3. A switch on port 1 of CLI#2 will
start/stop motors on CLI#1 & 3.
Thank you for your feedback.
Yves
|
|
| |
In lugnet.dacta, Yves Levesque wrote:
> Hi,
>
> Here is my first attempt to build a VB.NET DLL class to facilitate somehow the
> building of VB.NET programs that talk to the old ControlLab Interface "B",
> 70909.
>
> http://www.box.net/shared/xc44rksi2h
Thanks a lot for sharing. I have one of these interfaces but my main problem
with it (using Robolab) has always been the incredibly slow response to inputs
(press a touch sensor and wait about 1 second for the motor to stop).
Can you tell me anything about response times in your program?
Jetro
|
|
| |
In lugnet.dacta, Jetro de Chateau wrote:
>
> Thanks a lot for sharing. I have one of these interfaces but my main problem
> with it (using Robolab) has always been the incredibly slow response to inputs
> (press a touch sensor and wait about 1 second for the motor to stop).
> Can you tell me anything about response times in your program?
>
> Jetro
Hi Jetro,
This is the exact reason why I started this project.
I did try Robolab (V5.1 I think) and was very disappointed about the time
response.
Of course, If people don't know about Visual Basic (VB), there is some learning
if they want to use the proposed DLL in their own projects since it is NOT as
easy as Lego Logo or any graphical programming langugage.
But still, The VB certainly brings more power and you can build a pretty User
Interface with buttons and lights on your computer screen...
If you try my Installable Demos (Using the Setup), I did set the Scan Time to 50
ms which is very Fast. If you open the source of the Demos in VB.NET, you can
change this Scan Time to whatever you want.
The Demo 2 will give you a good idea of the response time at 50 ms since the
Output 1 follows the status of a switch connected to input 1.
The installable versions (setup) of the demos don't request to have VB.NET
installed, but you need to have MS .NET Framework 3.5 sp1 (free) which you might
already have. If demo 2 or 3 don't install, proceed to the installation of Demo
(1) first.
I believe I've read somewhere that the CLI sends updates of its inputs about
sixty times per second. So, I guess that a scan time of about 15-20 ms is the
fastest you can get for a user program.
Give some feedback if you try it.
Thank you.
|
|
| |
In lugnet.dacta, Yves Levesque wrote:
> In lugnet.dacta, Jetro de Chateau wrote:
> >
> > Thanks a lot for sharing. I have one of these interfaces but my main problem
> > with it (using Robolab) has always been the incredibly slow response to inputs
> > (press a touch sensor and wait about 1 second for the motor to stop).
> > Can you tell me anything about response times in your program?
> >
> > Jetro
>
> Hi Jetro,
>
> This is the exact reason why I started this project.
> I did try Robolab (V5.1 I think) and was very disappointed about the time
> response.
>
> Of course, If people don't know about Visual Basic (VB), there is some learning
> if they want to use the proposed DLL in their own projects since it is NOT as
> easy as Lego Logo or any graphical programming langugage.
>
> But still, The VB certainly brings more power and you can build a pretty User
> Interface with buttons and lights on your computer screen...
>
> If you try my Installable Demos (Using the Setup), I did set the Scan Time to 50
> ms which is very Fast. If you open the source of the Demos in VB.NET, you can
> change this Scan Time to whatever you want.
>
> The Demo 2 will give you a good idea of the response time at 50 ms since the
> Output 1 follows the status of a switch connected to input 1.
>
> The installable versions (setup) of the demos don't request to have VB.NET
> installed, but you need to have MS .NET Framework 3.5 sp1 (free) which you might
> already have. If demo 2 or 3 don't install, proceed to the installation of Demo
> (1) first.
>
> I believe I've read somewhere that the CLI sends updates of its inputs about
> sixty times per second. So, I guess that a scan time of about 15-20 ms is the
> fastest you can get for a user program.
>
> Give some feedback if you try it.
>
> Thank you.
That sounds very promising! I have absolutely no idea about VB. My idea was to
build something for a display at a LUG event which would require the interface
to be connected to a laptop. Unfortunately, the only laptop I have that has a
serial port (the other 'big' problem of the interface) runs windows 98 and
cannot run XP - Will that be a problem?
Otherwise, do you think your VB application will work over a USB-Serial
converter? (robolab doesn't - I've tried half a dozen different adapters).
Jetro
|
|
| |
In lugnet.dacta, Yves Levesque wrote:
> Hi,
>
> I just added a demo file in the folder http://www.box.net/shared/xc44rksi2h.
> It is called LegoMultiCLISetup.zip and contains the installable test application
> for multiple (Max 3) CLIs.
>
> I would appreciate if someone could try it with 2 or 3 CLIs at the same time and
> give me some feedback. I have only one CLI and cannot test this Multiple CLI
> control feature.
>
> Once installed, start the application, Select Com ports for the CLIs that are
> connected to your PC. Don't forget to put a "Checkmark" to the port you want to
> use.
>
> Press Start CLIs. Pressing a Switch on port1 of any CLI will start motors on
> port 1 of other CLIs. Release the switch to stop motor(s).
>
> Ex., If you use 3 CLIs, pressing a Switch on Port 1 of of CLI#1 will start
> Motors on port 1 of CLI#2 and CLI#3. A switch on port 1 of CLI#2 will
> start/stop motors on CLI#1 & 3.
>
> Thank you for your feedback.
>
> Yves
I did some quick testing on the LegoMultiCLI program that you posted. I was able
to connect two CLIs to my computer as follows:
CLI 1: connected to COM1 serial port
CLI 2: connected to COM6 (using USB to Serial adaptor)
I ran the program and selected the appropriate COM ports and then hit the Start
button. I had a touch sensor connected to port 1 on CLI 1.
When I pressed the touch sensor, the output 1 did start properly on CLI 2.
When I released the touch sensor though, the output remained on. The input
light on CLI 1 would toggle on and off with each press of the sensor, but the
output on CLI 2 only reponded to the first press.
I moved the touch sensor to CLI 2 and it had the same effect where the output on
CLI 1 only responded to the first press.
Any ideas?
I will try to get VB installed in the next couple days so that I can view the
source code files to help with some testing.
Brian
|
|
| |
In lugnet.dacta, Jetro de Chateau wrote:
>
> That sounds very promising! I have absolutely no idea about VB. My idea was to
> build something for a display at a LUG event which would require the interface
> to be connected to a laptop. Unfortunately, the only laptop I have that has a
> serial port (the other 'big' problem of the interface) runs windows 98 and
> cannot run XP - Will that be a problem?
> Otherwise, do you think your VB application will work over a USB-Serial
> converter? (robolab doesn't - I've tried half a dozen different adapters).
>
> Jetro
I have not had any problems using the CLI with a Startech USB-Serial converter
on my laptop (running WinXP). I have also used the converter successfully with
Robolab 2.5.4 and 2.9.
http://www.startech.com/item/ICUSB232-USB-to-RS232-DB9-Serial-Adapter-Cable-Male-to-Male-Serial-Adapter-USB-to-Serial.aspx
Brian
|
|
| |
In lugnet.dacta, Brian Bachmeier wrote:
>
> I did some quick testing on the LegoMultiCLI program that you posted. I was able
> to connect two CLIs to my computer as follows:
>
> CLI 1: connected to COM1 serial port
> CLI 2: connected to COM6 (using USB to Serial adaptor)
>
> I ran the program and selected the appropriate COM ports and then hit the Start
> button. I had a touch sensor connected to port 1 on CLI 1.
> When I pressed the touch sensor, the output 1 did start properly on CLI 2.
> When I released the touch sensor though, the output remained on. The input
> light on CLI 1 would toggle on and off with each press of the sensor, but the
> output on CLI 2 only reponded to the first press.
>
> I moved the touch sensor to CLI 2 and it had the same effect where the output on
> CLI 1 only responded to the first press.
>
> Any ideas?
>
> I will try to get VB installed in the next couple days so that I can view the
> source code files to help with some testing.
>
> Brian
Thank you Brian. I made a mistake and corrected it I think. So you can
download the updated file (same name) from the same url mentionned before.
But according to what your saying, it sounds good.
Thank you very much for your interest.
Yves
|
|
| |
In lugnet.dacta, Brian Bachmeier wrote:
> In lugnet.dacta, Jetro de Chateau wrote:
> >
> > That sounds very promising! I have absolutely no idea about VB. My idea was to
> > build something for a display at a LUG event which would require the interface
> > to be connected to a laptop. Unfortunately, the only laptop I have that has a
> > serial port (the other 'big' problem of the interface) runs windows 98 and
> > cannot run XP - Will that be a problem?
> > Otherwise, do you think your VB application will work over a USB-Serial
> > converter? (robolab doesn't - I've tried half a dozen different adapters).
> >
> > Jetro
>
> I have not had any problems using the CLI with a Startech USB-Serial converter
> on my laptop (running WinXP). I have also used the converter successfully with
> Robolab 2.5.4 and 2.9.
>
> http://www.startech.com/item/ICUSB232-USB-to-RS232-DB9-Serial-Adapter-Cable-Male-to-Male-Serial-Adapter-USB-to-Serial.aspx
>
> Brian
I am using a Prolific USB-Serial Adapter for my CLI project and it works great.
I am using it on a Dell Latitude E6500 with Win XP SP3.
I don't believe my VB solution will work on windows 98 because it needs the
Microsoft .Net Framework 3.5 sp1 which, I think, does not install on win98.
I understand that this solution is still NOT the ultimate solution since VB.NET
is not as easy as simple lego logo langage.
I did choose VB.NET because I currently use VBA (Visual Basic for application)
that comes as part of all MS Office applications (Excel, Access). VB.NET
express edition is Free and not that difficult to learn by ourself compare to
other langages. A lot of good ref exist on the net.
And it offers lots of possibilities. Not only it provides a way to make a
program to handle CLI's I/Os but it also gives a great Graphical User Interface
(GUI) where we can put Push Buttons and feedback indications, counters
indications etc... (try Lego70909DemoSource.zip to have a look at the GUI for
testing all CLI's I/Os).
I could eventually write a PDF document that explains, step by step with images,
how to build a Lego CLI application in VB.NET if people shows interest in
building their own lego CLI project using my VB.NET DLL.
If you tell me what exactly you want to do with your CLI at your LUG event (What
is connected to your CLI I/Os, How many CLIs, A functionnal description
explaining the logic in relation to all I/Os.), I would be glad to build a
program for you. As long as it is not a very long term contract ;-).
Yves.
|
|
| |
In lugnet.dacta, Yves Levesque wrote:
> In lugnet.dacta, Brian Bachmeier wrote:
> >
> > I did some quick testing on the LegoMultiCLI program that you posted. I was able
> > to connect two CLIs to my computer as follows:
> >
> > CLI 1: connected to COM1 serial port
> > CLI 2: connected to COM6 (using USB to Serial adaptor)
> >
> > I ran the program and selected the appropriate COM ports and then hit the Start
> > button. I had a touch sensor connected to port 1 on CLI 1.
> > When I pressed the touch sensor, the output 1 did start properly on CLI 2.
> > When I released the touch sensor though, the output remained on. The input
> > light on CLI 1 would toggle on and off with each press of the sensor, but the
> > output on CLI 2 only reponded to the first press.
> >
> > I moved the touch sensor to CLI 2 and it had the same effect where the output on
> > CLI 1 only responded to the first press.
> >
> > Any ideas?
> >
> > I will try to get VB installed in the next couple days so that I can view the
> > source code files to help with some testing.
> >
> > Brian
>
>
> Thank you Brian. I made a mistake and corrected it I think. So you can
> download the updated file (same name) from the same url mentionned before.
>
> But according to what your saying, it sounds good.
>
> Thank you very much for your interest.
>
> Yves
Brian, I just put in the BOX folder the LegoMultiCLISource.zip file that is the
Source for the Multiple CLIs test demo project.
Thank you again for your help.
|
|
| |
In lugnet.dacta, Yves Levesque wrote:
> In lugnet.dacta, Yves Levesque wrote:
> >
> >
> > Thank you Brian. I made a mistake and corrected it I think. So you can
> > download the updated file (same name) from the same url mentionned before.
> >
> > But according to what your saying, it sounds good.
> >
> > Thank you very much for your interest.
> >
> > Yves
>
>
> Brian, I just put in the BOX folder the LegoMultiCLISource.zip file that is the
> Source for the Multiple CLIs test demo project.
>
> Thank you again for your help.
The updated program works perfectly. At first I thought there was another issue
because one of the outputs (B) on the CLI with the touch sensor also went on....
but after checking the code I see you added that little surprise also (motorB on
CLI with touch sensor goes forward, motorA on other CLIs goes On Left).
Thanks very much for sharing your work. I can definitely imagine a lot of
different applications (train layouts with automated swtiches, lego contraptions
with many lights and motors etc).
I am not a Visual Basic expert but have written some simple programs in the
past, and the ability to easily program a nice windows interface is great.
Are you planning to put together some documentation (commands, declarations,
etc)?
Let me know if there is anything that I can help you out with, testing or
otherwise.
Brian
|
|
| |
In lugnet.dacta, Brian Bachmeier wrote:
>
> The updated program works perfectly. At first I thought there was another issue
> because one of the outputs (B) on the CLI with the touch sensor also went on....
> but after checking the code I see you added that little surprise also (motorB on
> CLI with touch sensor goes forward, motorA on other CLIs goes On Left).
>
> Thanks very much for sharing your work. I can definitely imagine a lot of
> different applications (train layouts with automated swtiches, lego contraptions
> with many lights and motors etc).
>
> I am not a Visual Basic expert but have written some simple programs in the
> past, and the ability to easily program a nice windows interface is great.
>
> Are you planning to put together some documentation (commands, declarations,
> etc)?
>
> Let me know if there is anything that I can help you out with, testing or
> otherwise.
>
> Brian
Thank you for your quick feedback Brian.
Indeed, I added the Output 2 that follows the switch connected to the same CLI.
I did it while correcting the mistake you pointed out.
I actually have a lego light connected on this output 2...
I am planning in my spare time to build a PDF document that will explain all
Methods, Properties, declarations, sample program...). I might start with a
quick guide that list the Methods and Properties first and I will improve the
document regularly with more explanations and images...
I will update the BOX folder regularly and post msg here about significant
updates.
I am glad it works with 2 CLIs. I hope the response time was as good as one
CLI. The interest for this VB.NET project, according to me, is really the
possibility to build a program that controls multiple CLIs to increase the the
quantities of I/Os while keeping a fast response time.
Thanks again!
Yves
|
|
| |
In lugnet.dacta, Yves Levesque wrote:
> Hi,
>
> Here is my first attempt to build a VB.NET DLL class to facilitate somehow the
> building of VB.NET programs that talk to the old ControlLab Interface "B",
> 70909.
>
> http://www.box.net/shared/xc44rksi2h
>
> This folder includes Source files and also setup files.
> To RUN the DEMO applications you need Microsoft .NET Framework 3.5 SP1 (FREE)
> already installed on your PC.
> To use the Source, you need Vusal Basic .NET 2008 Express Edition. (FREE)
I just uploaded a PDF document to the "Box" url mentionned in the first message.
This document (Lego70909DLL.pdf) is a tutorial on how to make ControlLab
Interface (CLI)project in VB.NET using the proposed DLL. It is also a reference
document that lists all Properties and Methods available from the CLI.
The document is in a preliminary stage and I will probably make some corrections
and I will also add some tips and tricks like how to add timing to CLI project
programs and how to make "One Shots" and more...
Yves
|
|
| |
In lugnet.dacta, Yves Levesque wrote:
> I just uploaded a PDF document to the "Box" url mentionned in the first message.
> This document (Lego70909DLL.pdf) is a tutorial on how to make ControlLab
> Interface (CLI)project in VB.NET using the proposed DLL. It is also a reference
> document that lists all Properties and Methods available from the CLI.
>
> The document is in a preliminary stage and I will probably make some corrections
> and I will also add some tips and tricks like how to add timing to CLI project
> programs and how to make "One Shots" and more...
>
> Yves
Thanks for the update. The documentation is well written and organized.
I look forward to future updates. If you need any help with testing or
anything, just drop me an email.
Brian
|
|
| |
In lugnet.dacta, Brian Bachmeier wrote:
> In lugnet.dacta, Yves Levesque wrote:
> > I just uploaded a PDF document to the "Box" url mentionned in the first message.
> > This document (Lego70909DLL.pdf) is a tutorial on how to make ControlLab
> > Interface (CLI)project in VB.NET using the proposed DLL. It is also a reference
> > document that lists all Properties and Methods available from the CLI.
> >
> > The document is in a preliminary stage and I will probably make some corrections
> > and I will also add some tips and tricks like how to add timing to CLI project
> > programs and how to make "One Shots" and more...
> >
> > Yves
>
> Thanks for the update. The documentation is well written and organized.
> I look forward to future updates. If you need any help with testing or
> anything, just drop me an email.
>
> Brian
I guess I found this a week too late - "MS Visual Basic .NET 2008 Express
Edition" has been replaced with a "2010" version now. MS .NET Framework has
also moved to V4.
Has anyone tried this with the new MS code? Which of the four VB packages
should I download? Choices are:
- Visual Web Developer 2010 Express
- Visual Basic 2010 Express
- Visual C# 2010 Express
- Visual C++ 2010 Express
I'm guessing it would be the second option, but I can't tell if it includes
support for VB.NET.
Thanks!
Eric.
|
|
|
