biztalk assembly checker

Question

Hello

 

Answer 1

Use the BizTalk Assembly Checker and Remote GAC tool (BTSAssemblyChecker.exe) to check the versions of assemblies deployed to the BizTalk Management database and to verify that they are correctly registered in the GAC on all BizTalk Server computers. You can use this tool to verify that all the assemblies containing the artifacts of a certain BizTalk application are installed on all BizTalk nodes. The tool is particularly useful in conjunction with a solid versioning strategy to verify that the correct version of a set of assemblies is installed on each BizTalk machine, especially when side-by-side deployment approach is used. The tool is available with the BizTalk Server 2009 installation media at Support\Tools\x86\BTSAssemblyChecker.exe.

Just a quick question as per the the documentation, you can verify any  BizTalk machine to verify that they are correctly registered in the GAC.  Check the setting to see if it is pointing to the correct machine.

-D

Answer 2

Hi,

The BTSAssemblyChecker.exe still checks the "old" GAC location for BizTalk assemblies. This makes it useless in BizTalk 2010.

The tool is aimed at Microsoft support personel and is not intended for "end-users". So I don't think it will not make much sense to report this issue to Microsoft support.

 

---

HTH,

Randal van Splunteren - MVP, MCTS BizTalk Server
http://biztalkmessages.vansplunteren.net

Please mark as answered if this answers your question.

Check out the PowerShell provider for BizTalk: http://psbiztalk.codeplex.com

Answer 3

Hi,

Randal is right there is no reason using this tool as it is aimed for earlier version of .NET framework. In .NET Framework 4.0, the GAC went through a few changes. The GAC was split into two, one for each CLR.  The CLR version used for both .NET Framework 2.0 and .NET Framework 3.5 is CLR 2.0. There was no need in the previous two framework releases to split GAC. The problem of breaking older applications in Net Framework 4.0. To avoid issues between CLR 2.0 and CLR 4.0 , the GAC is now split into private GAC’s for each runtime.The main change is that CLR v2.0 applications now cannot see CLR v4.0 assemblies in the GAC. It seems to be because there was a CLR change in .NET 4.0 but not in 2.0 to 3.5. The same thing happened with 1.1 to 2.0 CLR. It seems that the GAC has the ability to store different versions of assemblies as long as they are from the same CLR. They do not want to break old applications. For reference on explanation or why see this thread .

HTH

Regards,

Steef-Jan Wiggers
MVP & MCTS BizTalk Server
http://soa-thoughts.blogspot.com/
If this answers your question please mark it accordingly

 

---

BizTalk