Advantages of .NET DLL over VB6 DLL

  • Thread starter Thread starter Precious
  • Start date Start date
P

Precious

Hi,
We are planning to migrate our vb6 components (published in com+) to vb.net
dll. Front end (vb6) will remain the same. What are the advantages and
disadvantages, do's and don'ts, best pratices to follow?

Thanks and regards


J Justin
 
Well, that's quite a question that does not have a simple answer.

First, I'll say that while .NET applications can interoperate with COM
components (and vice versa), the full benefits of .NET aren't realized
unless you are in a complete .NET environment.

..NET is a completely different architecture from COM that provides better
performance, better scalability, less maintenance and more language choices
than COM. For example, VB 6 was not a true OO language and did not perform
as well as C. VB.NET is now fully OO and performs just as well as any other
..NET language.
 
Hi Precious,

Just start with searching this newsgroup on Com+.

The first answer you see than is from Jay B. Harlow.

It gives a good answer I think.

Cor
 
Thank you for your response. Infact, the main reason for my eager to migrate
only com components (published in com+) is this..., Whenever there is some
changes in our com+ server application, we have to the reinstall Application
Proxies at all client machines.
As I said earlier, we want to continue using existing front-end (vb6) as it
is.
By creating "serviced component in .net", is there any approach, so that I
can avoid creating application proxy everytime there is a change in com+
server application.

Thanks and regards


J Justin
 
Back
Top