Be aware of the difference, because they use a different strong name key as described in the Installation Instructions. It is also noticed on Codeplex.
It is a pity that the sample source code is running also into several errors regarding ‘different’ dll’s.
Just to share with you:
Error
Exception calling "SaveChanges" with "0" argument(s): "Unable to locate assembly "Microsoft.Practices.ESB.Resolver, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"."
At C:\projects\microsoft.practices.esb\Source\Core\Install\Scripts\ESBFunctions.ps1:350 char:28
+ $null = $exp.SaveChanges( <<<< )
Error
Exception calling "SaveChanges" with "0" argument(s): "Unable to locate assembly "Microsoft.Practices.ESB.Resolver, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"."
At C:\projects\microsoft.practices.esb\Source\Core\Install\Scripts\ESBFunctions.ps1:350 char:28
+ $null = $exp.SaveChanges( <<<< )
At the end the easiest way is to install from source code. If you install from the binaries, then you have to make sure your samples are referencing the right assemblies.
