Thanks again for your really quick responses.
I expect that as I work in VisualAPL, I'll rarely use strong typing. However, as I work with developers that are (so far!) non-APL programmers, I have to interact with other languages.
I haven't had many problems taking in .Net types and using them in VisualAPL, the only exception being ItemArray indexing.
I have had problems returning strongly typed variables to other languages, so I appreciate your help.
Thanks for letting me know that assignment by value (traditional APL assignment) preserves strong typing where possible. This may help, and I'll look at your example and explore this further.
I can appreciate you may need to tighten up VisualAPL internals from time to time, and I suspect most of them might be "transparent to the user". I would hope not too many changes would affect working code. When you say my experience trying to convert from a Cielo variable to string[,] was expected, it may have been expected by you, but it wasn't by me!
I am really looking forward to using VisualAPL in substantial ways in the very near future. The quick taste I've had of it illustrates how much faster and easier I can accomplish almost all tasks, compared to using C# and VB. Being able to return .Net types from VisualAPL is necessary for this to happen. Again, thanks very much for your quick help.