The BizTalk Server 2010 Beta is here!
Today we’re excited to announce the availability of the BizTalk Server 2010 Beta, which will RTM in the third quarter of calendar year 2010. BizTalk Server 2010 aligns with the latest Microsoft platform releases, including SQL Server 2008 R2, Visual Studio 2010 and SharePoint 2010, and will integrate with Windows Server AppFabric. This alignment, along with the availability of a wide array of platform adapters, allows customers to stitch together more flexible and manageable composite applications.
Updates include enhanced trading partner management, a new BizTalk mapper and simplified management through a single dashboard that enables customers to backup and restore BizTalk configurations. Also included in this release are new Business to Business integration capabilities such as rapidly on-board and easy management of trading partners and secure FTP adapter (FTPS) .
Download the beta today and tell us what you think at www.microsoft.com/biztalk.
Today we’re also officially launching Windows Server AppFabric, with the immediate availability of the Windows Server AppFabric Release Candidate (RC) at https://msdn.microsoft.com/appfabric; the final release of the product will be available in June.
Together with the already available Windows Azure AppFabric, Windows Server AppFabric and BizTalk Server 2010 form Microsoft’s application infrastructure technologies. These offerings benefit you by delivering cloud-like elasticity, seamless connectivity, and simplified composition for the most demanding, enterprise applications.
To learn more about Microsoft’s application infrastructure technologies, visit the Microsoft Application Infrastructure virtual launch event at www.appinfrastructure.com!
Comments
- Anonymous
July 22, 2010
Hi!Tried to open a Visual Studio BizTalk 2006 solution in Visual Studio 2010 and run the migration process to convert the solution to a BizTalk 2010 solution. But all I got on my project files was: Error converting project file. The element <BIZTALK> beneath element <VisualStudioProject> is unrecognized.Any ideas? - Anonymous
September 25, 2010
I'm also experiencing RonnieB's problem. Looks like a plain vanilla bug in the migration code. PLEASE Microsoft, fix this!