BizTalk Server 2009，Visual Studio 2008和Windows Server 2008兼容性问题 [英] BizTalk Server 2009, Visual Studio 2008 and Windows Server 2008 Compatibilty issue

问题描述

我已经开发了一个自定义Excel解码器组件，使用Windows Server 2008，visual studio 2008和BizTalk Server 2009将Excel文件转换为flatfile。所以当我尝试测试应用程序时，我收到的错误如"请验证管道强名称是正确并且管道组件在GAC中"。我已经尝试了所有可能的方法，例如使x86成为目标CPU和任何CPU等选项。甚至我已将Data Connectivity组件安装到机器中。我已将应用程序dll放入程序集和解码器组件dll到管道组件文件夹和Assembly文件夹。但是这些方法都没有帮助我解决这个问题。如果您有任何解决方案，请试着帮我吗？

当我尝试使用BizTalk server 2006的32位机器时，Windows Server 2003和Visual Studio 2005成功从excel文件转换为平面文件。

< p class = MsoNormal> 注意：问题在于64位机器只有我尝试过在32位机器上成功将excel转换为Flat文件。

请尽量帮我解决这个问题。是兼容性问题还是其他任何问题。

解决方案

您是否有可能在途中的某个位置更改了强名称密钥？我认为GAC可能有一个较旧的引用缓存，您的管道引用较新的强名称。在添加新版本之前，请务必删除旧的GAC版本以避免此问题。

另外，您是否使用项目属性对程序集进行签名或使用Delay签名作为构建过程的一部分？我不确定Delay签名是否适用于BizTalk项目。

感谢，

Hi ,

I have developed one custom Excel Decoder component to convert Excel file to flatfile using windows server 2008, visual studio 2008 and BizTalk Server 2009. So when i try to test the application i am getting the error like "Please verify that the pipeline strong name is correct and that the pipeline assembly is in the GAC". I have tried all the possible ways like making x86 is the Target CPU,and  Any CPU, etc option. Even I have installed Data Connectivity component into the machine. I have placed application dll into assembly and decoder component dll to pipeline component folder and Assembly folder. But none of the ways helped me in resolving the issue. Can you please try and help me if you have any solution?

But when I try the same with 32 bit machine using BizTalk server 2006, windows server 2003 and visual studio 2005 its successfully converted from excel file into Flat file. 

Note : The issue is with 64 bit machine only as I have tried and succeeded in converting excel to Flat file in 32 bit machine.

Please try to help me to resolve this issue. Whether is it compatibility issue or any other issue.

解决方案

Is it possible you changed the strong name key at some point along the way? I am thinking that the GAC might have an older reference cached and your pipeline refers to the newer strong name. Be sure to remove an old GAC version before adding a new one to avoid this problem.

Also, did you use the project properties to sign the assembly or use something like Delay signing as part of a build process? I am not sure if Delay signing works properly with BizTalk projects.

Thanks,

这篇关于BizTalk Server 2009，Visual Studio 2008和Windows Server 2008兼容性问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！