Posts

Showing posts from July, 2013

BTDF – Warning Assembly “……" depends on the following assemblies that must be installed in the Global Assembly Cache

Image
This post hopefully helps when facing the aforementioned error while depkiying, buildingwith the btdf. Problem warning : Assembly “……" depends on the following assemblies that must be installed in the Global Assembly Cache What is the dll we get the error on????? Follow the next step to get more info. Cause One or more of your projects have a reference to an Assembly, which has Copy ‘Local = false’. This causes the GacUtil called by MSBuild / BTDF to do it’s best to keep you busy.   Solution Open ALL your projects, look in every refence for the ‘Copy Local’ and change it to True Result EXEC : warning : Assembly "<>.Orchestrations, Version=1.0.0.0, Culture=neutral, PublicKeyToken=<>" depends on the following assemblies that must be installed in the Global Assembly Cache for runtime to succeed:   Assembly "Microsoft.Practices.ESB.ExceptionHandling.Schemas.Faults, Version=2.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"

BizTalk Solution Analyzer

Image
  The tool BizTalk Solution Analyzer allows you to analyse a BizTalk project and uses various rules to generate a report which contains information about your implementation, stored in a database so that you can do additional querying on it. It is also a perfect tool to be included in your build as it provides tasks to be included in MSBuild. This tool was created by Michael Stephenson and is packed with functionality. To use the tool, you need to; Create a new database Name it AppFx.SolutionAnalyser Import the scripts provided with the solution   Open AppFx.SolutionAnalyser (and change the settings where needed) The settings can be saved, and retrieved Explicitly define the output path by typing in the path (e.g. C:\BizTalk\Settings.Xml) The analysis should complete (if not, see the section below) And a report Html file is generated Which contains all the statistics The tool additionally provides reports which can be found at t

XLang – Debugging BizTalk from within VS.Net

Image
When developing Orchestrations, you are using a visual designer, which will in effect generate XLang which is handled by the BizTalk Xlang engine. Although the Xlang engine has its own language XLang, it does support some shapes (Expression shapes, Delay) which are compatible with C#. It’s also possible to call .Net assemblies from an Atomic scope, and debug these following the steps; described in this post: Debugging .Net ): Build the external C# library project Add it to the GAC Restart the Host Instance Attach the debugger to the Host instance All great stuff, additionally, you can use the Orchestration debugger ( Orchestration debugger ) which connects to the XLang scheduler, all fine and dandy. When you however, have an orchestration that directly fails, with an error you cannot comprehend, or tracking is disabled, you’re not so happy. Tracking is performed at the persistence points ( Persistence points ). An Expression shape (which does not lead to a

Scaling ...how they did it...how you can do it

One of the best tech-ed sessions in 2013 was from Haishi Bai who was discussing Patterns & Practices for Composing Cloud Services and was explaining a design pattern he was working on; As of now he is posting details on his pattern, and builds on concepts that already are highly recommended, but combined with cloud technologies allows you to prepare your applications for the future; VVM - Part1 VVM - Part2 One of the key components is that you should prepare for scale (scale-up, scale-out). As some companies already faced that challenge, i’ve posted some links where you can find their approach and experiences; NetFlix http://advance.blackducksoftware.com/content/WRNetflix DropBox http://techcrunch.com/2013/07/11/how-did-dropbox-scale-to-175m-users-a-former-engineer-details-the-early-days/ Facebook https://www.facebook.com/note.php?note_id=409881258919 Kind regards, Sander Tags van Technorati: Azure , Scale , VVM

BizTalk maps – problem solving scenarios

Image
If we consider the BizTalk architecture; from the 'BizTalk Server: Presentations Gallery' We can see that there are 3 possible places where your maps are executed (in classic BizTalk); Inbound (on the receive port) Outbound (on the send port) Business Process (within an orchestration) So if there any problems, which approach should we follow, which options do we have…I hope to answer this in the following section, and these are things to think about, it’s not enforced, or defined in a book, it just a good thing, to be aware of your options and have a strategy. Solving an BizTalk map issue in a live environment ; We have an issue, we know it is in the map (analysis of the exception, output) We let the team from ‘fixoursystem-land’ solve the issue in their dev, they test it before usage We deploy it to the test environment, they test it before usage (deployed by a dev/admin) We deploy it to the critical/live environment….(deployed by an admin) We need to ensure t