Following is from MSDN. But are some tuning but still your component should
work just fine without any changes.

Migrating to COM+
Now, what happens when you migrate an existing application to COM+ and it
uses CreateInstance? You should change those CreateInstance statements to
CreateObject or use the New keyword. Doing so will improve the performance
of your application because it will work directly with COM+ and avoid the
overhead of working with CreateInstance while it's really calling
CreateObject behind the scenes.
Once you have changed CreateInstance to CreateObject, you can take advantage
of other COM+ features. You should also create a reference to the COM+
Services Type Library to replace your reference to the MTS type library (see
Figure 1). The COM+ Services Type Library supports the same features as the
MTS type library, but has new methods that add more functionality. You will
still find good old GetObjectContext, SetAbort, and SetComplete there, but
you will find many more features as well.

T. Mahata

From: vishal.chopra@s...
[mailto:vishal.chopra@s...]
Sent: Friday, May 11, 2001 4:47 AM
To: professional vb
Subject: [pro_vb] Migration from MTS to COM+




Hi
We are migrating one of our application from Win NT to win 2k
The application has VB 6.0 dll's registered with MTS. We have to migrate
this to
COM+
I would like to know that

What changes have to be made in the DLL ??

Thanks in advance

Vishal