错误SIPEPS，版本5.0.0.0 = 4.0 UCMA VS2010 / VS2013 [英] Error SIPEPS, Version=5.0.0.0 UCMA 4.0 VS2010/VS2013
问题描述
我已经开发了两个VS 2013年和2010年VS的UCMA 4.0应用程序在运行时的项目，我得到这个错误：
I had developed an UCMA 4.0 application on both VS 2013 and VS 2010. When run project, I got this error:
莫非无法加载文件或程序集SIPEPS，版本5.0.0.0 =文化=中性公钥= 31bf3856ad364e35或它的一个依赖。该系统找不到指定的文件。
Could not load file or assembly 'SIPEPS, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
我用 .NET 4已设定的目标搭建平台，以 64 。由 dependwalker_x64 并没有文件丢失检查。
I used .NET 4 and had set target build platform to x64. Checked by dependwalker_x64 and no file is missing.
我还用从样品App.config文件但不能工作，所以我改变了App.config文件如下：
I also used the App.config file from Sample but not work so I had changed the App.config file as follow:
<runtime>
<assemblyBinding>
<dependentAssembly>
<assemblyIdentity name="SIPEPS" publicKeyToken="31bf3856ad364e35" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-4.5.0.0" newVersion="5.0.0.0"/>
</dependentAssembly>
</assemblyBinding>
我应该如何为这个做问题？非常感谢您的帮助！
How should I do for this problem? Thanks so much for any help!
推荐答案
唯一的例外可能是非常令人困惑，因为UCMA项目并不需要一个明确的参照本 SIPEPS DLL ，往往你会得到异常，即使你找到该DLL并将其移动到同一个目录作为您的应用程序。
The exception can be very bewildering because UCMA projects don’t require an explicit reference to this SIPEPS DLL, and often you’ll get the exception even if you locate the DLL and move it into the same directory as your application.
事实证明，它通常是由两件事之一引起的：
It turns out that it’s usually caused by one of two things:
- 您指定的.NET Framework版本错误。
- 您所定位的错误类型的CPU。
在Visual Studio中打开你的项目的属性，并确保.NET框架4.5被选中。
Open up the properties for your project in Visual Studio and make sure .NET Framework 4.5 is selected.
如果你没有运行Visual Studio 2012中，你有一个稍大
的问题，
If you’re not running Visual Studio 2012, you have a somewhat larger problem,
由于不能使用.NET 4.5和Visual Studio 2010和更早版本。
如果你有选择的框架的早期版本，改变它，重建项目，然后再试一次。 UCMA 4.0列出了.NET 4.5的要求。
because you can’t use .NET 4.5 with Visual Studio 2010 and earlier. If you had an earlier version of the framework selected, change it, rebuild the project, and try again. UCMA 4.0 lists .NET 4.5 as a requirement.
如果你仍然得到异常，检查目标平台，并确保它是对所有项目的任何CPU或x64 。 UCMA 只是因为3.0版本工作在64位机器，什么有时发生的是，一个项目将得到不经意间设置为86，所以会尝试加载SIPEPS的32位版本。 dll的启动时。那么，有没有SIPEPS.dll的32位版本;因此有点误导例外。
If you’re still getting the exception, check the target platform and make sure it is Any CPU or x64 for all projects. UCMA has only worked on 64-bit machines since the 3.0 version, and what sometimes happens is that a project will get inadvertently set to x86, and will therefore try to load a 32-bit version of SIPEPS.dll on startup. Well, there isn’t a 32-bit version of SIPEPS.dll; hence the somewhat misleading exception.
的参考
Reference
这篇关于错误SIPEPS，版本5.0.0.0 = 4.0 UCMA VS2010 / VS2013的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
