VB6 to VB.NET & Strong Naming

Discussion in 'ASP .Net' started by rob, Apr 28, 2004.

  1. rob

    rob Guest

    Dear All,

    We have a fairly big application that has to be converted from VB6 to
    VB.NET. The goal is to convert one component after the other and do some
    testing after each step. In a first approach one VB6 (ActiveX DLL) project
    was converted to VB.NET utilizing the automatic conversion of VS.NET.
    Besides the new dll other interop dlls have been created, i.e.
    Interop.ASPTypeLibrary.dll, etc. While the actuall dll is strongly named all
    the other generated interops are not strongly named and therefore cannot be
    put in the GAC. It seems the only way to get it to work is by removing the
    references and then adding them back in. This is extremly tedious as there
    are many interops and MANY projects that have to be converted. Is there a
    better way to do this?

    Once that sub-project is converted to VB.NET the other components have to be
    able to access it. In order to access a .NET assembly from a COM another
    interface has to be created. I did use regasm but then did get stuck on what
    to do further. Can anybody give me some general input on a good way to
    convert a big VB6 app to a VB.NET app? Links and comments are highly
    appreciated.

    Rob
     
    rob, Apr 28, 2004
    #1
    1. Advertising

  2. You can vastly reduce the amount that need to be converted by carefully selecting only the ones that are going to need to be modified for conversion. If there's a COM DLL that's written in VB6 and it isn't going to need to be changed, why convert it to VB6? There's no point, you don't gain anything. If you did your initial design of the VB6 project well, then there should be quite a lot of DLL-based functionality that falls into this category - if not, you haven't applied the principle of localization and encapsulation well enough when doing your VB6 work in the first place
    If there's stuff that's not going to need changing but may need adding to, consider wrapping VB6 COM DLLs in new, .NET library DLLs.
     
    =?Utf-8?B?Qm9uag==?=, Apr 28, 2004
    #2
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Ron Baakkonen

    Re: Using a strong named vb6 DLL in ASP.NET

    Ron Baakkonen, Nov 6, 2003, in forum: ASP .Net
    Replies:
    0
    Views:
    543
    Ron Baakkonen
    Nov 6, 2003
  2. Manuel Lopez

    Strong Naming an ASP.Net Project

    Manuel Lopez, Dec 1, 2003, in forum: ASP .Net
    Replies:
    6
    Views:
    1,426
    Chris Jackson
    Dec 2, 2003
  3. namekuseijin

    Re: "Strong typing vs. strong testing"

    namekuseijin, Sep 27, 2010, in forum: C Programming
    Replies:
    214
    Views:
    3,453
    Nick Keighley
    Oct 17, 2010
  4. namekuseijin

    Re: "Strong typing vs. strong testing"

    namekuseijin, Sep 27, 2010, in forum: Python
    Replies:
    229
    Views:
    3,547
    Gregory Ewing
    Oct 29, 2010
  5. Sachin Patil

    Strong Naming Fails for .NET 2.0

    Sachin Patil, Jun 6, 2006, in forum: ASP .Net Security
    Replies:
    1
    Views:
    221
    Nicole Calinoiu
    Jun 7, 2006
Loading...

Share This Page