Home Dashboard Directory Help
Search

VSSDK 2008/2010/2012 DTE.Events subscription problem (reproduceable) by Dessus


Status: 

Closed


1
0
Sign in
to vote
Type: Bug
ID: 775900
Opened: 1/6/2013 12:14:06 AM
Access Restriction: Public
0
Workaround(s)
view
1
User(s) can reproduce this bug

Description

Boxing and unboxing the DTE object doesn't allow event subscriptions to work in the VSSDK all the way back to vs2005 and up to vs 2012.

See my post here:

http://social.msdn.microsoft.com/Forums/en-US/vsx/thread/eb1e8fd1-32ad-498c-98e9-25ee3da71004

http://stackoverflow.com/questions/8775111/dteevents-onstartupcomplete-event-not-working-for-vspackage-vssdk2010/14180361#14180361

http://stackoverflow.com/questions/5405167/dte2-events-dont-fire/14180383#14180383

http://stackoverflow.com/questions/4816801/visual-studio-2010-extension-events-not-called/14180414#14180414

http://social.msdn.microsoft.com/Forums/en-US/vsx/thread/7ec92d44-afa0-4778-bea4-6cbdd658962c?prof=required
Details
Sign in to post a comment.
Posted by Dessus on 7/6/2013 at 4:15 PM
I believe this might have been caused by the fact that I had Embed Interop Types enabled as detailed by another user here: http://social.msdn.microsoft.com/Forums/vstudio/en-US/0b73b5a6-ed9b-40df-aadc-d1d5e3ed39f4/embed-interop-types in a dll (other than my plugin dll) I have that has reference to the VSSDK. This caused issues when passing the COM objects around. I suspect it was not referencing the same instances and this threw the eventing model, and later caused issues with Ninject (dependency Injection) for me. Possibly this is more of a usability bug, as it took me many months to track down the root cause.
Posted by Microsoft on 2/5/2013 at 10:53 AM
Hi Dessus, I haven't heard back on this so I'm going to go ahead and close it. Please reactivate as necessary.

Thanks, Tony Goodhew, Program Manager, VS Pro
Posted by Microsoft on 1/29/2013 at 10:34 AM
Hi Dessus, We are unable to repro this issue. Can you provide us with a small project that consistently reproduces the issue.

Thanks, Tony Goodhew, Program Manager, VS Pro
Posted by Microsoft on 1/8/2013 at 12:22 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 1/6/2013 at 12:51 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.