Visual Studio and .NET Framework Home
EnvDTE80.Windows2.CreateToolWindow2 doesn't return in the last parameter the hosted usercontrol if ComVisible attribute not set to true
Carlos J. Quintero
as By Design
6/14/2009 3:13:39 PM
User(s) can reproduce this bug
If the usercontrol class passed to the EnvDTE80.Windows2.CreateToolWindow2 method is not visible to COM, the usercontrol is created and hosted correctly in the toolwindow but it is not returned (by ref) as last parameter.
Visual Studio 2010 Beta 1
Operating System Language
Steps to Reproduce
- Create a VB.NET add-in with VS 2010 Beta 1 with the attached code.
- Notice that the ComVisible attribute of the assemblyinfo.vb has been changed from True to False.
- Notice that the ComVisible attribute has been added to the connect.vb class because it is required according to another bug that I reported (https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=467081)
- Notice that with these two changes, the UserControl1 class is not visible to COM.
- Run the add-in.
The last parameter of CreateToolWindow is returned null
The last parameter of CreateToolWindow should not be returned null because managed add-ins should not require anything related to COM.
If the UserControl1 class has the attribute ComVisible set to true (or it is set at assembly level), the last parameter returns the created usercontrol as expected.
TAP Code (if applicable)
You can indicate your satisfaction with how Microsoft handled this issue by completing this quick
3 question survey
to post a comment.
Please enter a comment.
on 6/17/2009 at 1:07 AM
Thanks for your feedback. We are routing this bug to the product unit who works on that specific feature area. The team will review this issue and make a decision on whether they will fix it or not for the next release.
Visual Studio Product Team
on 6/16/2009 at 2:59 AM
Sorry, please ignore the previous comment. We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
on 6/16/2009 at 2:53 AM
Thanks for the feedback, but we only accept feedback in English at this time. We are therefore closing this issue. We would greatly appreciate it if you could submit this issue again in English.
to post a workaround.
Please enter a workaround.
© 2014 Microsoft