Results 1 to 9 of 9
  1. #1
    Super Moderator jscher2000's Avatar
    Join Date
    Feb 2001
    Location
    Silicon Valley, USA
    Posts
    23,112
    Thanks
    5
    Thanked 93 Times in 89 Posts

    COM Add-in development (Office 2003)

    I currently have Office XP "developer edition" with Outlook 2003 installed over. I maintain an Outlook COM Add-in for our office, and I discovered that the key tools I need to do that carried over when I installed Outlook 2003. Specifically, I can open a project in the Outlook VBE, edit it, and make a new DLL. The package and deploy wizard has problems, and I can't save the project after making the DLL, but I have been able to live with these glitches.

    Now that I am going to rebuild my computer from scratch, with a full Office 2003 suite, I have a problem. There is no developer edition of Office 2003, so I seem to have some messy choices:

    Plan A is to install Office XP, configure it and update it. Then install Office 2003 over it, and configure and update that. It sounds like a lot of work and wasted drive space...

    Plan B is to install Office 2003, and also a copy of Visual Studio 2005 Standard that MS was kind enough to send me for sitting through some online tutorials. Problem is, I don't know from .Net framework, and having to do special wrappers or purchase VSTO to integrate with Office is well beyond my needs and budget. So this might not work for me.

    Plan C is to install Office 2003, and also an old copy of Visual Basic 6.0. I suspect that it does not integrate as nicely as Office Developer, but actually I've never tried it.

    Any suggestions?

  2. #2
    Gold Lounger
    Join Date
    Dec 2000
    Location
    New Hampshire, USA
    Posts
    3,386
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: COM Add-in development (Office 2003)

    Plan C is best way to go.

    Install VB 6, or Visual Studio with VB 6.
    Build the DLLs in VB, not VBA.
    This even facilitates supporting multiple versions of Office.

    You can use the PDW in VB 6, anf/or, better yet, use Inno Setup with ISTools.

    I always build in VB 6, and use VB 6 Forms instead of VBA Forms..

  3. #3
    Super Moderator jscher2000's Avatar
    Join Date
    Feb 2001
    Location
    Silicon Valley, USA
    Posts
    23,112
    Thanks
    5
    Thanked 93 Times in 89 Posts

    Re: COM Add-in development (Office 2003)

    Is there a converter to go from VBA forms to VB forms?

  4. #4
    Gold Lounger
    Join Date
    Dec 2000
    Location
    New Hampshire, USA
    Posts
    3,386
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: COM Add-in development (Office 2003)

    No.

    I started to write a converter a few years ago.

    AFAIK, conversion cannot be 100% automated.

    Manually converting a VBA form to a VB Form is tedious, but after one does a few, it's not really too difficult.

    Also, once the VBA forms are converted to VB forms, conversion to .NET forms will be automatic, other than for features done differently in .NET Forms.

    Initially, you could import the VBA forms into VB and use them as "Designers", but you should replace the Designers one by one as soon as you can.

  5. #5
    Gold Lounger
    Join Date
    Dec 2000
    Location
    New Hampshire, USA
    Posts
    3,386
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: COM Add-in development (Office 2003)

    I just took a look at the code I was working on 4+ years ago.
    It might be possible to do a physical conversion of a VBA userform to a VB 6 Form,
    but that would require lots more investigation.

    If it's possible, I expect somebody has already done it.

    Converting the underlying code is another matter.

  6. #6
    Gold Lounger
    Join Date
    Dec 2000
    Location
    New Hampshire, USA
    Posts
    3,386
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: COM Add-in development (Office 2003)

    Did you ever find a converter?

  7. #7
    Super Moderator jscher2000's Avatar
    Join Date
    Feb 2001
    Location
    Silicon Valley, USA
    Posts
    23,112
    Thanks
    5
    Thanked 93 Times in 89 Posts

    Re: COM Add-in development (Office 2003)

    I searched around, but eventually stopped looking. I'm going to have IT dedicate a machine to build DLLs using Office Developer XP. I can't really justify all the time to deal with VB at this point.

  8. #8
    Gold Lounger
    Join Date
    Dec 2000
    Location
    New Hampshire, USA
    Posts
    3,386
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: COM Add-in development (Office 2003)

    That's no fun.

    I've gotten my code to be able to convert a Word template to a VB project, but still has to manually go thru the code to make sure it works in VB, and VB appears to place controls on Forms differently than VBA places controls on Userforms, so some placements are a bit odd.

    MSFT makes this task needlessly difficult by omitting certain things fron the object model, e.g., no Properties collection for controls on a Userform.

    Migrating to .NET eliminates this nonesense as everything uses Windows forms.

  9. #9
    Super Moderator jscher2000's Avatar
    Join Date
    Feb 2001
    Location
    Silicon Valley, USA
    Posts
    23,112
    Thanks
    5
    Thanked 93 Times in 89 Posts

    Re: COM Add-in development (Office 2003)


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •