Three weeks ago, we released Visual Studio Tools for Apache Cordova Update 2. Last week, we introduced you to a new TACO CLI. Now we’re back with Update 3, which is automatically included when you install Visual Studio 2015. If you’re an existing user of Visual Studio 2015, you’ll receive a notification to download and install today.
This release significantly improves the tools’ stability by fixing 13 of the top issues reported on Stack Overflow. Here are three of the most notable changes reported by developers:
- Addresses blocking issue when trying to use the Tools for Apache Cordova along with the ASP.NET 5 Beta 7 release. (First reported by “Pablo Martinez”)
Previously, after installing ASP.NET 5 Beta 7, Cordova projects would fail when opening with an error message that says “An equivalent project (a project with the same global properties and tools version) is already present in the project collection…”
- Deploying to Windows Phone 8 devices now works when emulators are not installed. (First reported by “ando”)
Before this fix, Visual Studio showed an error saying that “no emulators are installed” and stopped deploying to the device.
- When working on an app for Android devices, an issue was fixed that caused a “could not reserve enough space for object heap” error. (First reported by “SpaMobile”)
Without this fix, an “Error occurred during initialization of VM; Could not reserve enough space for object heap” message appeared when using the Visual Studio Tools for Apache Cordova, targeting Android devices.
We’re hard at work already on the next update to the tools and we’ll see you back here on the blog soon. Thanks to everyone who’s been asking and answering questions on Stack Overflow (using the visual-studio-cordova tag) and we look forward to continuing to work with you there!
To stay up to date on these updates, news in the Cordova world, and more, follow us on Twitter (@VSCordovaTools). And as always, feel free to email us with your feedback (vscordovatools –at- microsoft.com), we enjoy hearing from you.
Jordan Matthiesen (@JMatthiesen)