Re: Uses for Screen OCR technology

Tech-Archive recommends: Fix windows errors by optimizing your registry



"Ajay Kalra" <ajaykalra@xxxxxxxxx> wrote in message
news:1158333218.223348.135340@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
You assume that its already not exposed. If you are using COM to expose
it, its likely already being done. I have no way of knowing internal
design, but I would strongly guess this is the case as this is how
functionality is usually exposed.

I would say they have all the polictical reasons to do it. MSFT has
said COM is dying a good death and instead they start using it to
develop its killer. If you read RichardG's site you will notice this
has been the trend in general by MSFT. One of the reasons .Net was
being promoted was that COM is too complex and is dead.


Ajay, we both know when a COM component is developed, it is not natural to
start with a a DLL with exported functions and wrap a COM interface around
it. Instead, the DLL itself has a class factory that creates the COM
objects. So if it's not natural for us, why do you think Microsoft would
have done it that way?

..NET exposes COM in a nice way, much like VB exposes COM in a nice way.
It's the nicest bridge possible from the app developer to COM. But it's a
bridge to, not a replacement for, COM.

COM might be dying as a natural result of the migration to managed code, but
to the extent .NET has not caught on as fast as MS had hoped, native C++/COM
are still alive.

-- David


.



Relevant Pages

  • Re: Memory Cleanup in .NET
    ... I have a COM dll which exposes an object CClient and has the interface ... This COM client is wrapped in a dlland the ... I have modified the code in this wrapper dll to do a SysFreeString(of ...
    (microsoft.public.dotnet.framework.clr)
  • Interface Design And Scalability
    ... I am "attempting" to develop an ATL COM DLL that exposes a large number of ... I also keep reading that I should group methods with related properties. ... If no...What if I the size of the DLL grows large and I want to use the ...
    (microsoft.public.vc.atl)
  • Problem retrieving object
    ... Each dll is specifically desgined so it exposes ... a third party control as a Control object. ...
    (microsoft.public.vb.winapi)
  • Re: create a wrapped managed dll that can be used from pure unmanaged code
    ... > I am trying to create a dll that internally uses managed types but exposes ... > a plain unmanaged interface. ... So that I would be able to use that dll from pure unmanaged ...
    (microsoft.public.dotnet.languages.vc)
  • Call VC++ functions from CSharp
    ... functions exposed by prev .dll. ... of structure and pointer to structures and enumeration. ... Is there any other possible way.to access exposes ...
    (microsoft.public.dotnet.framework.interop)