|
|
Is this still issue? Was the dev MonkeyMote that is currently developing his plugin for MM5 -- related to 0018953 ? |
|
|
Yes, I can still reproduce the steps and cause Visual Studio 2022 to crash. I don't see MediaMonkey5 Library in the References section of the project MMote gave me, so he's probably using something else to link to the MM5 COM. (Also because on his C++ project, when you click Add Reference, COM doesn't show up as an option.) |
|
|
Posted on the MS developer forum to hopefully obtain more insight on what's causing the crash: https://docs.microsoft.com/en-us/answers/questions/838727/adding-com-reference-crashes-visual-studio-how-do.html |
|
|
FYI: I can confirm the issue, when adding 'MediaMonkey5 Library' COM reference then the 'Task is canceled' error appears in Microsoft Visual Studio 2022: image.png (56,508 bytes) |
|
|
Note: Opening the "MediaMonkey5 Library" Type Library (from the Windows SDK https://developer.microsoft.com/en-us/windows/downloads/windows-sdk/) crashes oleview.exe as well. http://files.drakinite.net/2022-05-06_13-33-09.mp4 |
|
|
Fixed in 2622 |
|
|
Re-opened: As found by Jordan the fix somehow failed to propagate to 2622. On current SVN sources the "MediaMonkey.exe /elevate /regcomserver" fixes the issue, but installing 2622 still produces the "corrupted" type library. Using MediaMonkey.exe compiled from current SVN sources works to register the type llibrary all right. It is that multi-process compilation somehow causes the issue, to be find why.. |
|
|
Fixed in 2623 |
|
|
Verified 2624 Test note: Tested both installation of 2624 and manually starting "MediaMonkey.exe /elevate /regcomserver" |
- Anonymous
