Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CreateInstance failed in version 2.2.6 loaded into VS 2017 #82

Closed
cw2 opened this issue Jun 21, 2021 · 4 comments · Fixed by #83
Closed

CreateInstance failed in version 2.2.6 loaded into VS 2017 #82

cw2 opened this issue Jun 21, 2021 · 4 comments · Fixed by #83
Assignees
Labels

Comments

@cw2
Copy link

cw2 commented Jun 21, 2021

Hello,

at first, thank you all for the excellent work on this extension, I have been using it for ages :)

Unfortunately, it seems the latest version 2.2.6 has broken support for VS 2017 (Professional 15.9.36), because it fails to load with the following error "Could not load file or assembly 'Microsoft.VisualStudio.Shell.15.0, Version=16.0.0.0", for complete detail please see attached ActivityLog.zip.

I have downgraded to version 2.2.5 that works fine.

Thank you,

CW2

@cw2
Copy link
Author

cw2 commented Jun 21, 2021

I forgot to mention I also have installed Visual Studio Community 2019 (16.10.0) with the extension version 2.2.5 working fine. If the problem can be caused by this particular combination of installed VS versions, please let me know in case you need to test anything or provide more information (e.g. fusion log); I am familiar with VS extension development.

@pharring pharring self-assigned this Jun 21, 2021
@pharring pharring added the bug label Jun 21, 2021
@pharring
Copy link
Owner

Thanks for the bug report. I'm very sorry about that.
I think I know why that happened. I switched to reference the Dev16 SDK, believing it supported all downstream products. My bad. I guess I have to revert to an older SDK.

@pharring
Copy link
Owner

I switched to using the Dev14 (VS 2015) SDK pieces and verified that it now works on VS 2017.
Thanks again for the bug report.

@cw2
Copy link
Author

cw2 commented Jun 22, 2021

I have checked the new 2.2.7 version and it works fine in VS 2017.

Thank you for such quick fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants