The Prerequisite component installation remains a pain-less and efficient endeavor. Who remembers the pain that gathering all of the BizTalk Server 2004 prerequisites inflicted?
Below is the standard configuration screen that we are use to seeing with BizTalk Server 2006 Rx. Not too much has changed with the exception of MSMQT. This was another feature that was deprecated in BizTalk 2006. Microsoft has been pretty adamant about getting off of MSMQT as there were plans for its dismissal
So as I have previously stated, this is an evolutionary release so you will not find many actual BizTalk changes in Visual Studio. This includes:
- No new BizTalk Shapes
- No new Functoids
- The Expression Editor still is not re-sizable - This debate never gets old :-)
Something that you will notice different is that the "Development and Deployment" VS configurations are gone! You will now only have Debug and Release which aligns better with what .Net programmers are use to. It also simplifies some of the automated Build and Deploy configurations, when dealing with .Net Helper assemblies.
I had the opportunity to participate in a Microsoft BizTalk 2009 Brown Bag session and have made some ad-hoc notes which I am happy to share with you (Non-NDA):
- BizTalk Project System – New Project System is implemented as a Flavor of C# Project System. This should allow for smoother transitions for future versions of Visual Studio. The BizTalk project is now a first class citizen in Visual Studio.
- BizTalk Project can contain any item (not just BizTalk artifacts). This means that you can have a C# class in your BizTalk project and do not have to create a separate .Net project that BizTalk would call. Note there are a few minor issues with adding a new class in the current build of this Beta but it will be fixed.
- Debug and Release as default configurations as opposed to Development and Deployment
- Add Web Reference is not directly available on Project anymore. Need to access it through “Add Service Reference” dialog box.
- Migrated all BizTalk project and item templates to the new style (.vstemplate)
- Old style templates are still supported.
- Full Visual Studio integration for BizTalk project migrations. This integration supports both BizTalk 2006 (R1 and R2) to 2009 migrations. ( I plan on creating a separate blog post that deals specifically with migration).
- During migration, only .sln, btproj and btproj.user files are backed up as there are no fundamental changes to remaining artifacts.
- Support for conversion of projects checked into Source Code Control.
- Implemented entire BizTalk build system using MSBUILD.
- Support for incremental builds (only re-build what you need to rebuild - this will reduce some of the build times for minor changes to your project).
- Refactored all compilers to eliminate any VS Dependencies – can compile BizTalk projects without VS – Project Build Component in BizTalk install (for build server).
- Map, Schema(validate against sample instances) and Pipeline(programmatically) unit tests can now be executed from within Visual Studio.
- Currently you cannot debug a map that has an extension object – such as calling an external assembly – will be addressed in a future release. You can unit test it though.
- Currently(2009 beta) multi source maps cannot be united tested
- DEBUG and TRACE constants will work for c# classes in BizTalk projects.