Were using Robot 2002 to test a .NET C# application with no real problems. The majority of the classes require mapping, so Robot no longer knows what a pusbutton or edit control is, but once these have been mapped to the .NET classes they operate as expected. Inintally during an evaluation we were looking at VB.NET and seem to remember no real provlems. VB.Net and C# are extreamly similar so I wouldn't expect any problems.
In regard to Object ID's, I don't know about VB.NET but in C# you can no longer use ID as a search type as they are reallocated every time the applications are run. I suspect that the ID's are now system wide unique, and as such we have found that we have to use the less stable ObjectIndex.
We are using WinRunner to test a C# application and found the same thing - we can't use the "MSW_id" property to define the objects - we are forced to use the less-stable "label" field to define the object. I was trying to find out if any other automated tools (i.e. Robot or VisualTest) would work better than WinRunner. Looks like we're all in the same damn boat.
Dade Behring, Inc.