🚀 go-pugleaf

Ole: 

Well I understand that they don't want you making any promises.  That's SOP for most folks.  It's good to hear that you (& Adobe as a whole) are aware of some of the issues, and are looking into it.  Based on what I saw in my tests, it looks like as long as you set the reference, you can at least partially use it in VB.NET.  If the current COM based implmentation can be tweaked to get rid of the errors like the ones I mentioned above, I think that would be great & would hopefully be something that would be attempted in the near term.  To be a true player in the .NET world would require a .NET framework, and while it would be great to see it soon, I expect that level of effort to be significant enough to push it out till the next major release (bummer<g>). 

In some cases, the script code needs to change to run in VB.NET, and while it would be nice if you could provide code examples, running the code through the translation process can provide tips on where changes need to be made.  For example, setting the size or color of an object (places where you need an array) changes as follows: 

    myTF.GeometricBounds = Array("0p", "0p", "63p", "1.92i")     myColor.ColorValue = Array(100, 0, 100, 0)     myTF.GeometricBounds = New Object() {"0p", "0p", "63p", "1.92i"}     myColor.ColorValue = New Object(){100, 0, 100, 0}  

Anyway, I'll try to stay plugged in to track any updates to the scripting implementation.  (And if you need any guinea pig's - er- volunteer's to test stuff with VB.NET - I'd be interested)  Thanks again for your help, 

-- Greg