COM or .net Assembiles Why?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

I am currently working on desgin of architecture for a Data Analysis &
Graphical Display Tool Kit project.

I need to build different components for each Data Analysis Technique &
Graphical Display.

The above developed components need to be integrated/Accessed through both
..net and COM clients.

Can u please suggest me, How should i develop the components (i.e whether as
DLL/OCX or .net assemblies) and why?

Your answer is very much appreciated.

Thanks in advance.
 
sumanth said:
Can u please suggest me, How should i develop the components (i.e whether as
DLL/OCX or .net assemblies) and why?

Your answer is very much appreciated.
Click to expand...

Where is your application to be deployed?

If only on machines where .Net is installed you'd be in for far less work
(and less trying work IME) implementing one or more classes in a .Net
language than with that _old_ COM _stuff_.

Regards,
Will
 
Thanks William DePalo.

The application will be deployed on the systems, which have .net framework
preinstalled.

Can a .net assembly be accessed by a COM client, in such as case what will
be the compatability issues involved.

Thank you
Sumanth
 
Yes, they can if you want to, but only if you have the CLR installed on that
machine.

However it is not recommended practice to use .Net COM Interop to implement
funactionality that will ONLY ever be called by COM clients. You can still
use code compiled to /clr and exposing COM interfaces directly to do that if
you want to use .Net functonality in your implementation.

Ronald Laeremans
Visual C++ team
 
Thanks Ronald Laeremans for the Information.

Can u please suggest me an article, where i can know more about
Implementing .net assembly and exposing COM Interfaces.

Thank You
Sumanth
 
sumanth said:
Can u please suggest me an article, where i can know more about
Implementing .net assembly and exposing COM Interfaces.
Click to expand...

I like the treatment on interop issues found in the book "Essential Guide to
Managed Extensions for C++" (Apress ISBN:1-893115-28-3) by Challa and
Laksberg.

Regards,
Will
 
Back
Top