We're in the process of rewriting a Delphi Win32 app and the UI will probably be the last thing to go. In the mean time we need to ship our C# BO's exposed as a COM interface. If worst comes to worst I'll expose a COM visible interface and box/unbox my BO's properties/methods.
I don't want to use say a BuisnessListBase<BuinesBase> as a SafeArray[] on the COM client.
Has anyone used CSLA .NET with a COM client?
Personally what I try to do in these cases is to create a separate assembly that sits between the COM client and your real objects.
Client -> COM assembly -> business library
This helps avoid contaminating your real .NET business library with COM goo.
However, it does mean writing an assembly that has a lot of COM goo, and which acts as an intermediary between COM clients and your .NET objects - and that can take some effort.
Copyright (c) Marimer LLC