Recently, I've been lucky to get a chance to experience the flavour of the beta release of VDM 2009. I spent few hours playing with it. and here is my first impression about it:As a .NET developer, I can say that NI Vision Team succeeded to make it (.NET native component). In other words, all functions and methods now exist in NationalInstruments.Vision Namespace.You may notice that the old axCWIMAQVision is new replaced by the new architected Algorithms Namespace.Collection namespace is intensively used as an evidence for the royal class .NET behavious of the NI framework.Examples is now provided in both C# and VB (good news for C# geeks). The drwaback so far is the absence of .NET API documentations. Also reported bugs is not processed so far. I thnks the new version is a valuable investment that You won't waste your money in.

Machine Vision

Vision Development Module 2009, a first look (as a .NET Developer)

Recently, I've been lucky to get a chance to experience the flavour of the beta release of VDM 2009. I spent few hours playing with it. and here is my first impression about it:

As a .NET developer, I can say that NI Vision Team succeeded to make it (.NET native component). In other words, all functions and methods now exist in NationalInstruments.Vision Namespace.
You may notice that the old axCWIMAQVision is new replaced by the new architected Algorithms Namespace.
Collection namespace is intensively used as an evidence for the royal class .NET behavious of the NI framework.
Examples is now provided in both C# and VB (good news for C# geeks).

The drwaback so far is the absence of .NET API documentations. Also reported bugs is not processed so far.

I thnks the new version is a valuable investment that You won't waste your money in.

Waleed El-Badry MSc.,MCPD, ISTQB Certified Tester
Assistant Lecturer
Mechatronics Department
Faculty of Engineering
Misr University for Science & Technology

Message 1 of 1

(3,215 Views)