BizTalk 2010 Beta 1 & AppFabric RC
On the 20th , BizTalk 2010 Beta 1 was released , a day after the AppFabric RC.
We all know ( at least a bit ) about BizTalk , but regardless we shouldn’t disregard the Windows Server AppFabric which is a set of integrated technologies that make it easier to build, scale and manage Web and composite applications that run on IIS. Windows Server AppFabric targets applications built using ASP.NET, Windows Communication Foundation (WCF), and Windows Workflow Foundation (WF).
It provides out-of-the-box capabilities for you to easily build and manage composite applications, including:
- Enhanced design and development tools in Visual Studio to build rich composite applications
- Management and monitoring of services and workflows via integration with IIS Manager and Windows PowerShell
- Distributed in-memory application cache to improve application performance
If we’ll go to the Download of the Windows Server AppFabric RC , we’ll see that the file is 41.4 MB ( for each CPU version ) , which only makes you wonder if by SP2 of SharePoint 2010 , we won’t expect to have an integration between the both ( SPS2010 & AppFabric ) !
I know that the SPTeam said that they don’t expect that the SPS2010 will have support to WF 4 , but that doesn't mean it won’t integrate with something that does OR have a change of heart and add it like WCF & WF was supported in BT2006R2 ( as an AddOn )
Any way , the download of BT2010B1 is here , and here it is : BizTalk Server 2010 Beta
Ohh ,yeh , one more thing , it would have integration with the new Visual Studio 2010 ;) [ Like dahh :) ]
Visual Studio 2010 - The type or namespace name 'MyClassLibrary' could not be found
I have run across this message in the Beta Edition of Visual Studio 2010 , and I dismissed it as a Beta feature . But now with the release version , for me , that message was a bit out of place .
It seems that the solution , as far as I’m concern , is very simple , change the Target to “.NET Framework 4” and everything is going back to normal.
If you’ll look closely , you’d notice that the default is set to “.NET Framework 4 Client Profile”
The .NET Framework 4 Client Profile is a subset of the .NET Framework 4 that is optimized for client applications. It provides functionality for most client applications, including Windows Presentation Foundation (WPF), Windows Forms, Windows Communication Foundation (WCF), and ClickOnce features. This enables faster deployment and a smaller install package for applications that target the .NET Framework 4 Client Profile.
If you are targeting the .NET Framework 4 Client Profile, you cannot reference an assembly that is not in the .NET Framework 4 Client Profile. Instead you must target the .NET Framework 4. For more information, see Troubleshooting .NET Framework Targeting Errors.