I am pleased to inform that Windows Azure SDK 1.4 has been released as could be seen from Windows Azure Team Blog announcement.
What’s new in SDK 1.4
Well, I can say that there’re not many changes as the update from SDK 1.2 to 1.3.
Windows Azure SDK 1.4 Refresh is primarily a stability release addressing the below issues.
- Resolved an issue that caused full IIS fail when the web.config file was set to read-only.
- Resolved an issue that caused full IIS packages to double in size when packaged.
- Resolved an issue that caused a full IIS web role to recycle when the diagnostics store was full.
- Resolved an IIS log file permission Issue which caused diagnostics to be unable to transfer IIS logs to Windows Azure storage.
- Resolved an issue preventing csupload to run on x86 platforms.
- User errors in the web.config are now more easily diagnosable.
- Enhancements to improve the stability and robustness of Remote Desktop to Windows Azure Roles.
This finally solves the “CommunicationObjectFaultedException was unhandled” that I mentioned here.
Along with the new SDK, there’re also some new features enabled:
- Windows Azure Connect:
- Multiple administrator support on the Admin UI.
- An updated Client UI with improved status notifications and diagnostic capabilities.
- The ability to install the Windows Azure Connect client on non-English versions of Windows.
- Windows Azure CDN:
- Windows Azure CDN for Hosted Services: Developers can now use the Windows Azure Web and VM roles as”origin” for objects to be delivered at scale via the Windows Azure CDN. Static content in a website can be automatically edge-cached at locations through out the United States, Europe, Asia, Australia and South America to provide maximum bandwidth and lower latency delivery of website content to users.
- Serve secure content from the Windows Azure CDN: A new checkbox option in the Windows Azure management portal enables delivery of secure content via HTTPS through any existing Windows Azure CDN account.
Grab and download it here.