You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cordova.apache.org by GitBox <gi...@apache.org> on 2019/09/05 12:53:58 UTC
[GitHub] [cordova-windows] trajano commented on issue #327: VS2019 drops
.jsproj (UWP JS) support, VS2017 keeps working
trajano commented on issue #327: VS2019 drops .jsproj (UWP JS) support, VS2017 keeps working
URL: https://github.com/apache/cordova-windows/issues/327#issuecomment-528349307
Question about all of this. Considering that it still works in VS2017, there is still some development tooling for the "legacy" code. However, would you still be able to use the code generated from the old tooling?
Google is notorious for actually screwing up more enterprise application deployments because when it deprecates features, it actually breaks backwards compatibility of old applications. Microsoft at least provides workarounds that can co-exist with older executable for the most part (e.g. Internet Explorer still exists and can still run old ActiveX code from older applications).
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org