VB.NET or C# with IMAQ (here is the debate)

[wbadry]

Strange Title, isn't it?

    Let me be concised. Few days ago, a member of this form confronted a problem in implementing a ParticleFilter2 Method in C#. I dug into the code and thanks to easy documentations of IMAQ we tackled the problem.

   However, I found a very odd behavior, when using the same assembly with VB.NET, methods can be overloaded with no errors. But if I use the same method in C# (the same assembly is referenced), no such overloaded method exists !

   I can't call that a bug, as since these functions are based on interoperability of .NET and activeX, strange behavior is anticipated. So, thanks God that my language of preference is VB.NET

  The mentioned behavior contradicts what .NET is all about, it was meant to create any classes by any .NET language and be used with the others as the language created with.

   We hope that NI Vision team would reconsider refactoring the code for .NET to achieve the same behavior across all .NET languages.

    I've enclosed a solution I made with VS 2008 and IMAQ 8.6 to explain the point.

[cguzman]

Hi Waleed,

You are not the only customer who has requested a better .NET solution in the NI Vision Development Module and customer feedback is very important to us. Expect good news in the near future 

Carlos Guzman

Software Group Manager

National Instruments 

[wbadry]

Thanks Carlos for responding. This is very expected from such a marvelous team of NI.