Windows Azure Toolkit for Eclipse July 2013 Preview includes a number of enhancements that make it easier for Eclipse developers to work with Windows Azure.
New features in this release includes:
A new “auto option” for the Windows Azure Storage account selection in the JDK and server deployment configurations–that “enables you to postpone the selection of a specific Storage account until you publish the deployment using the Publish to Azure dialog,” explains Microsoft.
“The Windows Azure Storage account you select in the Publish Wizard is used when you’re ready to publish. This is an enhancement to the automatic upload of a chosen JDK and App Server to Windows Azure storage that was enabled in the May 2013 release.”
It’s also now possible to deploy a complete cloud application to a new Azure storage account within Eclipse –using the new button added in the Add Storage Account dialog, creates a new Windows Azure Storage account without having to leave the Eclipse UI.
Also added new features for larger deployments, that brings the ability to specify a local storage resource as the deployment destination for JDK and application server, in case your deployment may be too large to be contained in the default approot folder, as is sometimes the case with larger JBoss and JDK v1.7 deployments.
Additionally, for large deployments, Microsoft now support new high-memory A6 and A7 Windows Azure Virtual Machines.
And, the new options for “Service Endpoints” of the Windows Azure cloud you target added. “Service endpoint options for this release are the global Windows Azure platform, the Windows Azure by 21Vianet, China, or a private Windows Azure platform,” Microsoft added.
Finally, update to Windows Azure Libraries for Java Package, based on version 0.4.4 of the Microsoft Windows Azure Client API is also available. “This package contains the latest SDK distribution and their open-source dependencies as an Eclipse library,” informs Microsoft. “Add this library to the build path of your project (not the Windows Azure project) and all relevant Windows Azure API libraries will be automatically referenced and included in your WAR file,” Microsoft adds.
You can download and install the Windows Azure Plugin for Eclipse with Java here.
And, the Team Explorer Everywhere 2012,Eclipse and Cross-Platform client for Team Foundation Server is released.
Microsoft notes, that the next major version of Team Explorer Everywhere is slated to release in the coming months. And, will bring usability enhancements adding into the Visual Studio Team Explorer along with important features such as transparent symlink support on Unix file systems and better integration with eGit for projects that are hosted in TFS but with a Git rather than TFVC source control repository.
Some major updates included in this release are:
- Improved folder compare performance when doing server to server paths went down from hours to seconds for certain queries but performance was improved in all scenarios including the most common local to server.
- Execute bit fix that was not automatically set on download onto some Unix based systems when talking to a TFS 2012 Update 1 or Update 2 server.
- Reliable uploads of large files with added support for chunked uploads of files. “When checking in really large files, the likelihood of an issue forcing the connection to get lost increases. On premises this is hardly ever an issue but when on the public internet this can be a big pain,” explains Microsoft.
- Support for TFS 2013 Preview, as well as the hosted service, TFS 2012 and TFS 2010.
- Support for Eclipse Kepler (4.3) and works all the way back to Eclipse 3.5
- Support for FreeBSD in Team Explorer Everywhere (particularly the command line client to TFVC) with added native code to support FreeBSD on 32 and 64-bit Intel architectures.
Also an update to the TFS SDK for Java with all these fixes in Java API is available.
Also, released today is the Windows Installer PowerShell Module 2.2.1, which updates to version 2.2.0 and comes with many new cmdlets including: “cmdlets to select records from a table or custom query, run ICEs on a package, and install, repair, or uninstall packages.”
In addition, the install, repair, and uninstall cmdlets also display progress, warning, and error information. Some issues were fixed as well.
snap-in installer has been removed in favor of the module installer – a per-user install that will upgrade any previous version. “You may also install the package to a per-machine location, though elevation is required,” informs microsoft. “This will make the module accessible to any host for any user on the machine.”
Download version 2.2.0 from CodePlex.