Of course you could use a C# wrapper instead of a VB wrapper, then the application would be in C#.
But that is just silly, and the important thing to do here is to focus on: [1] Business Requirements (what really needs to get done here). [2] Education (if this guy is objecting to things which would still be issues when using DLLs or SQL or any other such thing it is probably because he does not know how to do his job). [3] Politics (basically, making sure that you stay friends with the people responsible so that when additional issues come up you are aware of them). If there is a need for C# interfaces to your code, you need to understand those requirements and design and implement appropriate interfaces. But that work would be needed even if you originally implemented in C#. Good design does not just "happen" because you choose to code in C#. And, in fact, if your original code was in C# this might be even harder (except that you might need to have some C# expertise to design good interfaces -- though for the most part I think you can get away with using VB). Seriously, though, this kind of thing is like arguing about the color of your socks. Yes, sometimes it matters, but it is rarely important for the business. -- Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
