DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 3 of 3

Thread: Migrating from MTS to COM+ (is recompile necessary)

  1. #1
    TL Bannon Guest

    Migrating from MTS to COM+ (is recompile necessary)

    I have a large number or MTS components created using VB6 installed on an NT
    server. I am researching our migration to Win2K server and have a few
    questions.

    If I use the export facility in MTS to create .PAK files, will I need to
    rebuild the MTS components on a 2000 Box? Without rebuilding, MTS
    components appear to install, but I receive -429 error when trying to run
    from a simple test harness. Is this due to missing dependencies? I can
    successfully run my test harness if I rebuild the components. I've had
    wonderful luck opening my MTS projects on a 2000 Box and recompiling
    (relying on reference mapping) then installing in COM+.

    I am not planning on initially changing objCTX.CreateInstance to
    CreateObject since I want backward compatibilty during the transition.
    Essentially, I would like to keep the code identical with the only
    difference being the OS of the Build Box.

    Need and MTS component, open on NT station.... need COM+....go to the Win2K
    or XP , open and compile. I am lucky (lucky??) enough to have dual
    enviornments.

    On another note, setting up remote components in MTS was as easy as adding a
    new computer while in the MMC. How is this accomplished with COM+?

    Any and all feedback is welcome.
    Thanks,
    Trac








  2. #2
    Chris Xia [MS] Guest

    Re: Migrating from MTS to COM+ (is recompile necessary)

    No recompile is not necessary. You do not even have to change
    objctx.createinstance that would work as it is. You can add a new computer
    in a similar way in COM+ MMC snap-in by just right clickng on computers
    folder to New Computer.


    HTH,
    Harris
    Microsoft

    --
    Please do not send email directly to this alias. This alias is for newsgroup
    purposes only.
    This posting is provided "AS IS" with no warranties, and confers no rights.


    "TL Bannon" <TBannon@kpmg.com> wrote in message
    news:3e1dbbc5$1@tnews.web.devx.com...
    > I have a large number or MTS components created using VB6 installed on an

    NT
    > server. I am researching our migration to Win2K server and have a few
    > questions.
    >
    > If I use the export facility in MTS to create .PAK files, will I need to
    > rebuild the MTS components on a 2000 Box? Without rebuilding, MTS
    > components appear to install, but I receive -429 error when trying to run
    > from a simple test harness. Is this due to missing dependencies? I can
    > successfully run my test harness if I rebuild the components. I've had
    > wonderful luck opening my MTS projects on a 2000 Box and recompiling
    > (relying on reference mapping) then installing in COM+.
    >
    > I am not planning on initially changing objCTX.CreateInstance to
    > CreateObject since I want backward compatibilty during the transition.
    > Essentially, I would like to keep the code identical with the only
    > difference being the OS of the Build Box.
    >
    > Need and MTS component, open on NT station.... need COM+....go to the

    Win2K
    > or XP , open and compile. I am lucky (lucky??) enough to have dual
    > enviornments.
    >
    > On another note, setting up remote components in MTS was as easy as adding

    a
    > new computer while in the MMC. How is this accomplished with COM+?
    >
    > Any and all feedback is welcome.
    > Thanks,
    > Trac
    >
    >
    >
    >
    >
    >
    >




  3. #3
    Narayana Pakala Guest

    Re: Migrating from MTS to COM+ (is recompile necessary)


    Hi

    This is further info.

    Microsoft recommends recreating the packages, if not recompile. Please check
    this:
    ---------------------------------------------------------------------------
    Consider Installing Windows 2000 from Scratch
    When installing Windows 2000, you can choose to either install the system
    from scratch or to upgrade the current configuration. In the latter case,
    the Windows 2000 installer will actually migrate the preexisting configuration
    to the new installation, including transforming MTS Packages into COM+ Applications.
    Installing Windows 2000 on a clean system and recreating the packages manually
    is recommended. This will prevent further propagation of preexisting configuration
    glitches.

    Why
    Our experience with upgrades suggests that the time saved (by not reconfiguring
    the server) is not worth the guarantee that you are not carrying any spurious
    state (broken or dirty object registrations, clogged directories, and so
    on) into the new environment.

    There are exceptions, of course. Depending on the role of the machine, you
    may decide that you prefer to preserve state through the upgrade—if you are
    upgrading a primary domain controller for example. However, application servers
    usually don't maintain much local state and therefore are good targets for
    "fresh installs."

    More Information
    When planning an upgrade, you should always check the Windows 2000 Planning
    and Design Guide in the Windows 2000 Server Resource Kit. The deployment
    guide lists the supported upgrade paths for Windows 2000 Professional, Windows
    2000 Server, and Windows 2000 Advanced Server, and describes other factors
    that may affect your decision to upgrade rather than to perform a clean install.
    (Keep in mind that the term "upgrade" means to replace the operating system
    using the upgrade features of Windows 2000. A clean install refers to formatting
    the disk and reinstalling the operating system and all applications.) It
    then discusses tools and procedures for automating the operating system upgrade
    process.
    ---------------------------------------------------------------------------
    Check the UEL: http://msdn.microsoft.com/library/de..._migration.asp

    Watch the the url wrap

    Best Regards
    Narayana


    "Chris Xia [MS]" <xwscom2@online.microsoft.com> wrote:
    >No recompile is not necessary. You do not even have to change
    >objctx.createinstance that would work as it is. You can add a new computer
    >in a similar way in COM+ MMC snap-in by just right clickng on computers
    >folder to New Computer.
    >
    >
    >HTH,
    >Harris
    >Microsoft
    >
    >--
    >Please do not send email directly to this alias. This alias is for newsgroup
    >purposes only.
    >This posting is provided "AS IS" with no warranties, and confers no rights.
    >
    >
    >"TL Bannon" <TBannon@kpmg.com> wrote in message
    >news:3e1dbbc5$1@tnews.web.devx.com...
    >> I have a large number or MTS components created using VB6 installed on

    an
    >NT
    >> server. I am researching our migration to Win2K server and have a few
    >> questions.
    >>
    >> If I use the export facility in MTS to create .PAK files, will I need

    to
    >> rebuild the MTS components on a 2000 Box? Without rebuilding, MTS
    >> components appear to install, but I receive -429 error when trying to

    run
    >> from a simple test harness. Is this due to missing dependencies? I

    can
    >> successfully run my test harness if I rebuild the components. I've had
    >> wonderful luck opening my MTS projects on a 2000 Box and recompiling
    >> (relying on reference mapping) then installing in COM+.
    >>
    >> I am not planning on initially changing objCTX.CreateInstance to
    >> CreateObject since I want backward compatibilty during the transition.
    >> Essentially, I would like to keep the code identical with the only
    >> difference being the OS of the Build Box.
    >>
    >> Need and MTS component, open on NT station.... need COM+....go to the

    >Win2K
    >> or XP , open and compile. I am lucky (lucky??) enough to have dual
    >> enviornments.
    >>
    >> On another note, setting up remote components in MTS was as easy as adding

    >a
    >> new computer while in the MMC. How is this accomplished with COM+?
    >>
    >> Any and all feedback is welcome.
    >> Thanks,
    >> Trac
    >>
    >>
    >>
    >>
    >>
    >>
    >>

    >
    >



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center