As Visual Studio 2013 become RTM and Azure SDK 2.2 supports it, you should support it also in Windows Azure BizTalk Services SDK since it currently only support VS2012
It is really necessary ASAP.57 votes
We know you guys are working on stabilizing the API's, it will be useful if you can release the full set of API's soon.5 votes
Although BizTalk services is a new feature of Windows Azure I expected more managebility in the management portal.
Here are some small examples -
- No start/stop on a source
- No enable/disable of a destination
- You can't double click on a tracking log
I'm currently using a tool by Steef Jan that enables me to do more with a Visual Studio Add-in than I can do with the portal... (http://social.technet.microsoft.com/wiki/contents/articles/22075.windows-azure-biztalk-service-explorer.aspx)3 votes
Basically reusable integration artifacts, aimed at speeding time to deployment of the most common SaaS integration scenarios, they are like the BizTalk accelerators for SWIFT & healthcare.
I have seen support for these in Dell Boomi & IBM Castiron for a while, reviewing the recent magic quadrant for IPAAS several competing platforms like SAP Hana Cloud Integration (HCI) & Skyvva are making significant improvements in this space.
If Microsoft were not to deliver cloudstreams then perhaps creating a marketplace/framework for partners to develop these and make them easily consumable by integration customers from Azure maybe an option.1 vote
- Don't see your idea?