-
Notifications
You must be signed in to change notification settings - Fork 16
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
Extension not loading in VS2019 16.1 and above due to use of deprecated APIs #30
Comments
I just want to ask whether there's any progress here, or whether we can help / contribute to get this issue fixed? |
Dang. I think it possible that I just need to do an official build and deploy. Allow me to look into it tonight and get back to you.
Sorry for the delay.
Ken
… On Nov 6, 2019, at 10:01 AM, Markus Schaber ***@***.***> wrote:
I just want to ask whether there's any progress here, or whether we can help / contribute to get this issue fixed?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#30>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADH3NUFQUIMFM6YV7ARU4ETQSLE4TANCNFSM4IIUQ44Q>.
|
@markusschaber Could you try the build for VS 2019? Just unzip and double-click. |
So to be clear, @markusschaber , I have reproduced your problem. I can install the older version using the above workaround, and am trying to resolve the above problem (though my C#/VS skills are minimal). We will be expanding the team very soon, so if we cannot get a better solution soon we will have a team in place that should be able to handle it soon. Sorry it is taking so long. Assembling the team is proving to be somewhat more time consuming than I originally anticipated. |
I have deleted a lot of the previous blather. I should really not respond till I collect more information... Here is a version of the package which should work. I was able to reproduce the problem, and managed to figure out the solution. Sorry again for the delay. We are working on that. I am leaving this open until it has been successfully uploaded to the marketplace. |
Ha. Figures. I can build for one or the other currently. I will look into making it do both, but due to some changes that we had to make recently it might be easier just having two separate installs. I'll work at it a bit over the next few days, but will have a new release built either that does both, or two separate versions that are both up to date soon. Thanks for the help! |
Thanks for your great work! |
@markusschaber I'm really sorry it took me so long to get back to you. Could you try this version on your VS 2017 instance: |
It installed without errors in VS 2017 (and did not offer to install in VS 2019). A small smoke test (Auditing 87 packages in solution) also seemingly worked fine. |
Version 3.4.0 (that you linked in this discussion) is working great in VS 2019. Thanks for building this great extension. |
Still getting this with VS2019 using latest deployed extension 3.0.5 ... any plans to publish new? |
Since this has STILL not been updated to install properly from within the VS extensions window, and the zip in the post above does not contain an installer like the VS2019 version does (in a higher post above), can someone please explain how to manually install the VS2017 zipped version? |
This change to how Visual Studio loads extensions affects audit.net:
https://devblogs.microsoft.com/visualstudio/updates-to-synchronous-autoload-of-extensions-in-visual-studio-2019/
The extension needs to be updated to use the new background load method:
https://github.com/microsoft/VSSDK-Extensibility-Samples/tree/master/AsyncPackageMigration
The text was updated successfully, but these errors were encountered: