How can we help you today? How can we help you today?

Visual Studio 2017 Extension Upgrade Re-Installed Android NDK?!?!?

So recently I had an update pending for Regate SQL Change Automation Core. When it went to install it was hanging for quite a while, then I noticed it was installing the Android NDK?!?!? I updated my NDK location a while back and for some reason the Regate SQL Change Automation Core Install did not respect this, and wanted it in the default location for some reason (i.e. C:\Microsoft\AndroidNDK64\android-ndk-r13b), now I have two NDKs installed... I assume this is an oversight / bug that should be fixed.

Here are some screenshots: (I have also attached my extension installation log).




Maxeta
0

Comments

5 comments

Sort by
  • Dan B
    Hi Mexeta,

    Thanks for posting on the Redgate forums.

    I will investigate this with the dev team and come back to you as soon as possible.
    Dan B
    0
  • Dan B
    Hi Mexeta,

    After reviewing this further this appears to be an issue with the VSIX installer rather than with the Redgate tooling. I would advise you reach out to Microsoft to see if they can help you to resolve this one.
    Dan B
    0
  • Alex Morgan

    Yeah, that definitely sounds like an oversight. The installer shouldn’t be forcing the default NDK path, especially if you've already updated it. I had a similar issue while working on a setup for getmodsapk.com — having two NDKs caused all kinds of confusion. Hopefully, they patch this in the next update. Thanks for sharing the logs and screenshots, super helpful!

    Alex Morgan
    0
  • williamoliverkcyu6c

    Yeah, that definitely sounds like an oversight — ideally the installer should respect your updated NDK path instead of forcing a default install. Having two NDKs can get messy, especially when different tools start referencing different locations. Reporting it as a bug to the vendor would be the best move here. For quick checks and references, I usually keep resources like http://onlinesassastatuscheck.co.za/ handy — makes it easier to stay organized when dealing with updates and fixes.

    williamoliverkcyu6c
    0
  • Luiz0022

    Yeah, that definitely sounds like an oversight — ideally the installer should respect your updated NDK path instead of forcing a default install. Having two NDKs can get messy, especially when different tools start referencing different locations. Reporting it as a bug to the vendor would be the best move here. For quick checks and references, I usually keep resources like Surflix APK handy — makes it easier to stay organized when dealing with updates and fixes.

    Luiz0022
    0

Add comment

Please sign in to leave a comment.