Cannot load add-ins with VS 2005 Beta 2

[developer]

We created an add-in project with VS 2005 Beta 1 that allowed us access to
various forms through our own "Code" command menu. After upgrading to Beta 2
our add-in no longer loaded or showed up in the add-in manager. After some
investigation, I found that changing the HostApplication Name in the
Deploy.AddIn file would allow VS to see the add-in. The problem now is that
VS throws an 'Attempted to read or write protected memory' error when loading
the add-in and crashes when trying to access our "Code" menu. Anyone know
how to remedy this, or why add-ins from Beta 1 do not work as is?

[Bob Butler]

Post by developer
We created an add-in project with VS 2005 Beta 1 that allowed us

--
<response type="generic" language="VB.Net">
This newsgroup is for users of Visual Basic version 6.0
and earlier and not the misleadingly named VB.Net
or VB 200x. Solutions, and often even the questions,
for one platform will be meaningless in the other.
When VB.Net was released Microsoft created new newsgroups
devoted to the new platform so that neither group of
developers need wade through the clutter of unrelated
topics. Look for newsgroups with the words "dotnet" or
"vsnet" in their name. For the msnews.microsoft.com news
server try these:

microsoft.public.dotnet.general
microsoft.public.dotnet.languages.vb

</response>

[developer]

Ok, thanks.

Post by Bob Butler

Post by developer
We created an add-in project with VS 2005 Beta 1 that allowed us

--
<response type="generic" language="VB.Net">
This newsgroup is for users of Visual Basic version 6.0
and earlier and not the misleadingly named VB.Net
or VB 200x. Solutions, and often even the questions,
for one platform will be meaningless in the other.
When VB.Net was released Microsoft created new newsgroups
devoted to the new platform so that neither group of
developers need wade through the clutter of unrelated
topics. Look for newsgroups with the words "dotnet" or
"vsnet" in their name. For the msnews.microsoft.com news
microsoft.public.dotnet.general
microsoft.public.dotnet.languages.vb
</response>