Dotfuscator 搞乱了 .net cf 2.0 应用程序
我最近继承了一个 .net 2.0 紧凑框架应用程序，我之前为其制作了一个可以正常工作和安装的点融合发行包。目标操作系统为windows mobile 2003及以上版本，最高可达6.5。
最近修复了一些错误后，我开始使用与前一个版本完全相同的构建项目来发布新版本。现在，我发现 .net 框架错误的点模糊版本错误如下
“应用程序无法加载所需的组件。 如果.net框架安装在存储卡上，请确保该卡就位并再次启动应用程序。如果失败，建议重新安装 .net 紧凑框架。支持信息：-27147454964 (8000700C)“
我不知道是什么原因造成的。据我所知，自上次发布以来构建解决方案没有变化，这很好，并且对应用程序源代码的更改仅包含其他内容如果我在不使用 dotfuscator 的情况下构建安装包，那么该应用程序可以正常工作，
因为我对 dotfuscator 的经验很少。 。
预先感谢
I have recently inherited a .net 2.0 compact framework application for which I have previously produced a dotfuscated release package that works and installs fine. The target OS in windows mobile 2003 and above up to 6.5.
Having made some bug fixes recently I have come to doing a new release using exaclty the same build project as for the previous one. Now I find the dotfuscated version errors with a .net framework error as follows
"The application failed to load required components.
If the .net framework is installed on a storage card, please ensure this card is in place and launch the application again. If this fails, a re-installation of the .net compact framework is recommended. Support info: -27147454964 (8000700C)"
I have no idea what could be causing this. As far as I am aware the build solution is unchanged since the last release which was fine and changes to the source code for the application consist of nothing more than refreshing a drop down list more often in certain circumstances. The application works fine if I build the installation package without using dotfuscator.
I hope someone can help with this as it's got me stumped. I have very little experience with dotfuscator which doesn't help.
thanks in advance
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
如果不深入研究更多细节，很难说。如果您仍然遇到此问题，请联系 PreEmptive 支持人员：[电子邮件受保护] 或在支持论坛上发布帖子，网址为 http://www.preemptive.com/forum/ 我们可以直接与您联系，尝试确定此问题的原因。
——布兰登·西格尔，先发制人的解决方案
It's hard to say without digging into more detail. If you are still having this problem, please either contact PreEmptive support at [email protected] or post a thread on the support forums at http://www.preemptive.com/forum/ where we can follow up with you directly to try to determine the cause of this problem.
--Brandon Siegel, PreEmptive Solutions
好吧，我已经弄清楚了这一点。它与 DLL 的签名有关。我必须延迟 DLL 的签名，然后让 dotfuscator 使用为延迟签名命名的相同密钥文件在 dotfuscations 后对它们进行签名。
Well I got to the bottom of this one. It was relating to signing of DLL's. I had to delay signing of the DLL's and then have dotfuscator sign them post dotfuscations with the same key file named for delayed signing.