The CodeAdvisor and the Migration Wizard both seem to give similar
information, but neither one seems to understand anything about how to
convert a VB6 Addin (which used a designer module for the connection) to a VB
2005 Addin for MS Project.
Is there any good documentation available on how I can do this? Or even some
good documentation about making Addins for Office applications other than
Word/Excel/Outlook? The Shared Addin seems to be the way to go (it has a MS
Project choice) but seems to be largely undocumented (at least at first
search).
Thanks,
Evan S. Dictor
[quoted text, click to view] "Paul Clement" wrote:
> On Thu, 4 May 2006 15:01:02 -0700, Evan S. Dictor <EvanSDictor@discussions.microsoft.com> wrote:
>
> ¤ I have an existing MS Project Addin (DLL) written in VB6. I would like to
> ¤ convert this application to VB2005. My preliminary attempts at migration have
> ¤ failed, mostly on the .dsr file that links the DLL to Project.
> ¤
> ¤ Is there anything I should know before I go any further (and by "any
> ¤ further" I guess I really mean "do anything," since I really haven't done
> ¤ much at all so far) with the process?
>
> You may want to run the Visual Basic 6.0 Code Advisor against your application before attempting to
> convert.
>
>
http://msdn.microsoft.com/vbasic/previous/2003/downloads/CodeAdvisor/ >
>
> Paul
> ~~~~
> Microsoft MVP (Visual Basic)