-
Notifications
You must be signed in to change notification settings - Fork 60
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
Upgrade Extension Package to AsyncPackage #206
base: master
Are you sure you want to change the base?
Conversation
Move from VisualStudio 2008+ => VS2015+
* This will allow updates to be published to Extension Market place & usage of the newer API's * Drops support for Visual Studio versions pre 2015
This looks great!! Can someone review? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't comment on the code but I cloned and built the project using VS 2019 v16.2.3
But, built the project with upgrading WindowsTargetPlatformVersion to 10 and PlatformToolset to v142
The VSIX works perfectly on VS 2019 with Xunit 4.2.1
I think I will need to create a new AxoCover entry in the marketplace, since this would break the old VS support, and I would like to avoid that. |
@chrish619 Thanks for that work - works like a charm. I pulled it to my repository to be used with other features and just build my local vsix package and using it on daily basis. Thanks |
I'd love to see this on VS marketplace. |
Author of that plugin does not really respond on any comments. I really don't know what needs to be done to put that on VS Marketplace - I don't even know if I am allowed to put that under new name/account. Noone really want to take Axodox's glory :) |
Since this plugin version is no longer compatible with old VS I think it should be uploaded as a separate entry in VS marketplace (e.g. AxoCover Next). Unfortunately I am having some health issues since last year, and it is hard for me to even do what is needed at my workplace, much less for free time. At this point the best way would be to create an organization on github, and let the community manage AxoCover in the future. |
@axodox , sorry to hear that. I really hope you will get better 😟. I don't have much time and all that things 'organisation on github' is new to me. But if I will find enough time then I will be happy to try that. Thanks for permission |
Fixes #204
Breaking changes
Other changes
*.11
requires*.10
, requires*.9
etc