I managed to get the reference added in Visual Studio 2022, you might like to test it, but it appears to be working here. Still can't get my application to work as there have been some changes, but I've posted another thread about that.

Thanks. :)

Sorry, we just found that the fix has failed to propagate to 2622, will be in 5.0.3.2623 ( https://www.ventismedia.com/mantis/view.php?id=17897#c68029 )

That would be really great!

Just FYI: Will be fixed in the next build 5.0.3.2622

Sorry about that. I've moved it to 5.0.4 and [url=https://docs.microsoft.com/en-us/answers/questions/838727/adding-com-reference-crashes-visual-studio-how-do.html]posted on the MS developer forum[/url] in case someone can help figure out what exactly is causing VS to crash.

I notice that this has been again pushed back, now to 5.1. I appreciate that there are a lot of other things to do and fixes aren't always easy, but I'm disappointed that after a year I've still not been able to get my application to work with MM5.

Perhaps I should have re-written it at the beginning after all.

I'm sure this isn't news because there was no mention of this issue in the list of updates, but I tested
MediaMonkey_5.0.3.2600_Debug.exe

found here:
https://www.mediamonkey.com/forum/viewtopic.php?f=6&t=86639&sd=d

and the problem remains when trying to add the COM reference.

No problem. You could, but it's likely not necessary.

Also, for additional context: The reason it was deferred to 5.0.3 was because the priority was initially low. Someone else posted the same issue on [url=https://www.mediamonkey.com/forum/viewtopic.php?f=27&t=100410]this thread[/url], and since it's clear multiple people are waiting for a fix on that issue, it was bumped up just a few days ago.

For what it's worth, I have this issue in Visual Studio Community Edition 2019.

If you need me to install a later version of VS Community to test, I'll be happy to do that.

Thanks!

Hi,
I escalated as asked Dev to feedback on estimate and set roadmap.

[quote=bensynnock post_id=492738 time=1641229670 user_id=60484]
I think it's due for a fix in 5.0.3. I would guess that there are higher priorities.
[/quote] You are right it was pushed due the priorities.

I think it's due for a fix in 5.0.3. I would guess that there are higher priorities.

I have the same issue.

The ticket describes the issue as
Priority: immediate
Severity: major
Reproducibility: always

and yet it has been 8 months and noone seems to be looking at it.

The entire com API is completely broken and noone wants to fix it? Weird.

For now, anyone who wants to use MediaMonkey with VoxCommando must remain on MM version 4. It's a shame.

I can reproduce the issue on Visual Studio 2017; tracked as https://www.ventismedia.com/mantis/view.php?id=17897. Sorry about the trouble. Is your project for a separate application that runs alongside MM, or for an addon that will run within MM? If it's the latter, it may be worth trying out using JavaScript for the addon, which will let it be used on multiple platforms when it comes time for Mac MM. :grin: