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

Warning on Open with VS2019 Plugin #204

Open
DylanCottell opened this issue Jul 29, 2019 · 1 comment · May be fixed by #206
Open

Warning on Open with VS2019 Plugin #204

DylanCottell opened this issue Jul 29, 2019 · 1 comment · May be fixed by #206

Comments

@DylanCottell
Copy link

When opening Visual Studio 2019 with the new version of AxoCover, I get a warning saying "Visual Studio did not load one or more extensions that were using deprecated API's". It doesn't seem to affect anything however, and just seems to be a weird quirk.

@chrish619
Copy link

There is a PR to "solve" the issue with 2019 targets, #191

But seems like there is more work required to get this on the market place & Visual Studio 2019 16.1+

From @madskristensen:

https://devblogs.microsoft.com/visualstudio/updates-to-synchronous-autoload-of-extensions-in-visual-studio-2019/

By default, Visual Studio 2019 v16.1 blocks any synchronously autoloaded package from any extension and shows a notification to alert the user about it.

and:

Here’s a bullet list to sum it up:

  • Marketplace requires autoload to be async and in the background
  • Users and IT admins can opt out of the blocking behavior (not recommended)
  • Autoloading extension should always happen asynchronously in the background

AsyncPackages are usable in VisualStudio 2015 (and above)
https://github.com/Microsoft/VSSDK-Extensibility-Samples/tree/master/AsyncPackageMigration

I can contribute to this issue, as I would also love to use AxoCover in VisualStudio 2019.

@chrish619 chrish619 linked a pull request Aug 13, 2019 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants