🚀 go-pugleaf

I've figured out how to access ID from VB.NET (at least some of the time).  Here's some results from the same code translated to VB.NET: VB.NET (debug build): ' timings: in IDE, @ 850 MHz, 500x: ' displayed - Seconds: 21.723 - per ad: 0.043 ' minimized - Seconds: 18.215 - per ad: 0.036 

' timings: compiled, @ 850 MHz, 500x: ' displayed - Seconds: 28.480 - per ad: 0.057 ' minimized - Seconds: 20.160 - per ad: 0.040 

VB.NET (release build): ' timings: in IDE, @ 850 MHz, 500x: ' displayed - Seconds: 28.152 - per ad: 0.056 ' minimized - Seconds: 18.258 - per ad: 0.037 

' timings: compiled, @ 850 MHz, 500x: ' displayed - Seconds: 24.125 - per ad: 0.048 ' minimized - Seconds: 16.066 - per ad: 0.032  Note that in VB.NET, you can decide to build an EXE with debug information or without it (release mode).  My first tests were with it (I think that it's the default), and I was very upset with the 74% increase in time required for the compiled/minimized code.  Once I noticed the setting & retested the release version, it showed a big improvement, but is still 38% slower than the VB6 code - NOT GOOD!  I expect that this may be partly due to .NET having to switch back and forth between the new .NET architecture and the old COM architecture.  It's too bad that there's such a performance hit.  There are other problems in using the ID object model in .NET - I've written more info over in the "ID Windows scripting w/ VB.NET" thread.  Briefly, though, it doesn't look like it's ready for use that way. 

-- Greg