>I am currently writing an article on Visual Studio extensibility, one
> that also covers Visual Studio.Net 2005. As of Beta 1 of VS2005, there
> appears to be some bugs with the Code Model support. Perhaps Microsoft
> insiders on this group might be kind enough to shed some light on these
> issues:
>
> 1) Both FileCodeModel.CodeElementFromPoint() and
> TextPoint.CodeElement() methods throw a TargetInvocationException when
> a matching CodeElement of the specified kind cannot be found at the
> specified TextPoint. In VS2003, these methods simply return a null
> reference, which is the desired behavior.
>
> 2) Visual Basic 2005 now supports the DocComment property on the Code*
> interfaces. That's great news. However, Visual Basic implements this
> property somewhat differently than C#. C# returns the XML comment
> block associated with the code element as a well-formed XML document,
> wrapped in a single <doc> root node. Visual Basic, however, simply
> emits the XML comment block as is, without a root node. Are there
> plans to make the implementations consistent?
>
> 3) Visual C++ 2005 appears to only have limited support for Code Model.
> The DocComment property, in particular, is read-only. The
> CodeFunction interface also is unable to identify a method as a
> constructor. Are there plans to bring the Code Model support in C++ in
> line with other languages?
>
> Any help would be greatly appreciated. Thanks.
>