Charles-- I'm not sure what you mean about it being obvious to .NET clients that a RCW is using COM interop unless by "clients," you mean "customers."
However, if your goal is to deploy a single DLL that exposes both COM interfaces and managed extensions, then John Noss is correct. You can use the tools in System.EnterpriseServices to write managed classes that support COM+ and act as wrappers for your unmanaged ATL-based classes. This will ultimately only require a single code base and most of the wrapper classes could probably be written by a code generator and then cleaned up for type inconsistencies. I recommend using tlbimp as a quick and not particularly dirty solution if you don't need to deploy as a single DLL. --Jekke Charles Gamble wrote: > > Yes, can I use Enterpise Services and also maintain the same codebase for > my C++ clients? > Basically I would like to keep my normal C++ COM+ objects and create .NET > wrapper objects in the same DLL using the same codebase. > Not sure about using TLBIMP as it is then obvious to .NET clients that it > is using COM Interop. > I would like to expose true .NET wrapper objects to our .NET clients. > > Thanks again, > Charles. > > =================================== > This list is hosted by DevelopMentorŪ http://www.develop.com > Some .NET courses you may be interested in: > > NEW! Guerrilla ASP.NET, 26 Jan 2004, in Los Angeles > http://www.develop.com/courses/gaspdotnetls > > View archives and manage your subscription(s) at http://discuss.develop.com -- NOTICE: If received in error, please destroy and notify sender. Sender does not waive confidentiality or privilege, and use is prohibited. =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 26 Jan 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
