You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 13, 2024. It is now read-only.
Pardon if this is not the right spot to report this bug.
It seems like there has been a regression in the handling of Toolsets in VS 15.3. I have a project where I told VS to use the "Global Cordova" in the config.xml editor and when I open the solution I get a prompt that the "Project needs to be updated for VS 2015". Agreeing to the "update" resets to the 6.3.1 Toolset, and adds an extra set of <engine> tags set to the versions in the Toolset. If I set this back to "Global Cordova" the extra <engine> tags remain and I am again prompted with the "Project needs to be updated for VS 2015" the next time I reopen the solution.
Selecting "No" to the upgrade prompt makes the project entirely unusable in VS. Selecting "Yes" and undoing the changes to config.xml seems to work fine, but it is quite a papercut to have that prompt and revert every time I open the solution and need to work with the Cordova project.
The text was updated successfully, but these errors were encountered:
I can confirm this still occurs with both 15.5.7 and 15.6.1.
Steps to reproduce:
create an Azure VM "Visual Studio Enterprise 2017 (latest release)", note this will as of today create a 15.6.0 VM, you can optionally update this to a newer version (example: 15.6.1)
Create a new blank cordova app in Visual Studio
Open the config.xml
In toolset, choose Global Cordova version
Save all and close solution
Open solution again
Result:
VS popup saying "Your Cordova projects needs to be updated to work with Visual Studio 15"
As described by WorldMaker with the yes/no options.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Pardon if this is not the right spot to report this bug.
It seems like there has been a regression in the handling of Toolsets in VS 15.3. I have a project where I told VS to use the "Global Cordova" in the config.xml editor and when I open the solution I get a prompt that the "Project needs to be updated for VS 2015". Agreeing to the "update" resets to the 6.3.1 Toolset, and adds an extra set of
<engine>
tags set to the versions in the Toolset. If I set this back to "Global Cordova" the extra<engine>
tags remain and I am again prompted with the "Project needs to be updated for VS 2015" the next time I reopen the solution.Selecting "No" to the upgrade prompt makes the project entirely unusable in VS. Selecting "Yes" and undoing the changes to config.xml seems to work fine, but it is quite a papercut to have that prompt and revert every time I open the solution and need to work with the Cordova project.
The text was updated successfully, but these errors were encountered: